Problem description¶
Create an input YAML file to run a HofX3D application using aircraft in-situ observations from the AEROMMA field campaign. To compute H(x) values, you can use the VertInterp observation operator. More details about this operator can be found in the documentation and in the examples within the fv3-jedi code repository. This observation operator extracts model values along the aircraft path.
The code snippet below shows the obs space section of the input YAML for this exercise. A few points to note:
obs space -> simulated variableslists all variables from the observation file that the JEDI executable will use. In the TEMPO example, which variables were included in this section?The
VertInterpoperator uses the YAML file specified under theobservation alias fileto map between the variable names in the observation file and the corresponding names used in the JEDI model space. The observation variable names follow the IODA naming conventions.The vertical coordinate in the observation file, pressure in this example, is specified under
obs operator -> observation vertical coordinate.
- obs space:
name: Aircraft
obsdatain:
engine:
type: H5File
obsfile: >>obsname_aeromma<<
obsdataout:
engine:
type: H5File
obsfile: >>obsname_aeromma_out<<
simulated variables:
- nitrogendioxideInsitu
obs operator:
name: VertInterp
observation alias file: ../inputs/geometry_input/name_map.yaml
variables:
- nitrogendioxideInsitu
vertical coordinate: air_pressure
observation vertical coordinate: pressure
interpolation method: log-linearAfter running the application, view the output feedback file and take note of the variables listed under ObsValue and under hofx.
Next, add ozone to the observation operator to extract the ozone values along the aircraft path. To find the observation variable name you can check the IODA naming conventions. After running the JEDI executable, examine the output feedback file and compare it to the previous feedback file. Note how ozone hofx is stored in the feedback file.