Incorporate adpsfc DA into JEDI for RRFS

[delippi]

Description

The UFO in JEDI is the component that not only computes model-simulated observations, but also houses filters and methods for observation QC, ob errors, and bias correction. The GSI observer is the equivalent. Many forward operators for various observations have been developed for the UFO. These operators can be utilized in RDAS. However these operators still must be tested for RDAS. The steps for transition by observation platform are as follows:

1. Establish IODA processing
2. Establish operator in UFO
3. Establish YAML input file
4. Validate with test assimilation experiments
5. Create ctest, if necessary
6. adpsfc data includes bufr obtypes=*81

Requirements

To create yaml configurations for assimilating adpsfc data.

Acceptance Criteria (Definition of Done)

• Phase 1 validation (hofx validation using GSI-IODA and GSI-geovals as necessary; GSI vs FV3-JEDI)

• Phase 2 validation (QC validation; no reliance on GSI except to be used as the baseline; GSI vs FV3-JEDI)

• Phase 3 validation (FV3-JEDI and GSI vs MPAS-JEDI)

• Link any relevant pull requests here:

Dependencies

None

[delippi]

Phase 1 update: (for 181/281)
Phase 1 results are in. These results were created using GSI-IODA, but allowing JEDI to handle the rest (geovals, QC, and oberror inflation). ObsErrorFactorConventional is included in these yamls, but it is turned off.

Uncertainties:

• For airTemperature: I had to use 1/2 obs error provided in errtable and commented out the ObsErrorPressureCheck to match ObsError in GSI.
• For stationPressure: Ob counts different a lot since JEDI rejects from the gross checks. When using GSI-QC, increments look really bad. The final result (with lower ob counts) allowing JEDI to handle the QC checks seems okay.

airTemperature

specificHumidity

stationPressure

winds