Updating native 4D-Var to IODA observation files converter #5
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This PR updates the native ROMS to the IODA-type observation files converter,
roms2ioda.m. The generic JEDI data assimilation framework uses the IODA-type observation files. It is an enhanced NetCDF-4 with first-level grouping and the extension nc4 for differentiation.Usually, one IODA-type file is available for each variable in the control vector, like SSH, SST, SSS, HF radar velocities, temperature, and salinity files for a particular data assimilation cycle. A file can include multiple variables representing vectors (u- and v-momentum) and spectral data with exact coordinates (lon, lat, depth, time). It may also contain multiple scalar variables if at the precise location, such as T and S profiles or biological profiles for various ecosystem state variables. I may also include secondary variables to compute a control variable with an elaborate operator. This setup gives us a lot of flexibility for filtering and averaging operators.
The native ROMS 4D-Var data assimilation operators are being restructured to allow multiple IODA-type files. This facilitates area-averaged and/or time-averaged H(x) operators that compute model solutions at the observation locations. This capability will be available soon.
The main objective of the restructuring is to have IODA-type observation files that can be used either in the native ROMS 4D-Var drivers or in any of the ROMS-JEDI data assimilation algorithms. Also, sophisticated H(x) operators will be available in the native ROMS 4D-Var algorithms. For more details, please check myroms/roms#62.
For example, the IODA-type NetCDF-4 schema for SSH observations that require an area-averaged (60 km) and time-averaged (36-hour) filter in the H(x) operator is as follows:
For HF radar velocity observations at a depth of 2 m, which computes an H(x) with a 24-hour time-averaged filter :
These IODA-type observation files are easily generated with the
roms2ioda.mconversion script:Note
The native ROMS 4D-Var file
usec3km_roms_obs_20190827.ncis converted to six IODA-type NetCDF-4 files.