IO: Difference between revisions
From WikiROMS
Jump to navigationJump to search
Created page with "<div class="title">ROMS I/O</div> ROMS uses NetCDF for all its input and output data management. The NetCDF files can be processed using the standard library developed by UNI..." (change visibility) |
No edit summary (change visibility) |
||
| Line 1: | Line 1: | ||
<div class="title">ROMS I/O</div> | <div class="title">ROMS I/O</div> | ||
ROMS uses NetCDF for all its input and output data management. The NetCDF files can be processed using the standard library developed by UNIDATA, the Parallel-IO (PIO) developed at NCAR, or the Software for Cashing Output and | ROMS uses NetCDF for all its input and output data management. The NetCDF files can be processed using the standard library developed by UNIDATA, the Parallel-IO (PIO) library developed at NCAR, or the Software for Cashing Output and Reads for Parallel I/O (SCORPIO) library intended for the DOE's Energy Exascale Earth Model System ([https://e3sm.org/scorpio-parallel-io-library/ E3SM]). The SCORPIO library was forked from the PIO library several years ago and evolved separately. The generic interface parallel I/O in ROMS works for both the PIO or SCORPIO libraries. However, we recommend using the PIO library because it is more efficient in processing I/O in our benchmark tests. | ||
Revision as of 02:11, 9 April 2021
ROMS I/O
ROMS uses NetCDF for all its input and output data management. The NetCDF files can be processed using the standard library developed by UNIDATA, the Parallel-IO (PIO) library developed at NCAR, or the Software for Cashing Output and Reads for Parallel I/O (SCORPIO) library intended for the DOE's Energy Exascale Earth Model System (E3SM). The SCORPIO library was forked from the PIO library several years ago and evolved separately. The generic interface parallel I/O in ROMS works for both the PIO or SCORPIO libraries. However, we recommend using the PIO library because it is more efficient in processing I/O in our benchmark tests.
