search

MetOffice / opsinputs

JEDI library generating VarObs and Cx files
BSD 3-Clause "New" or "Revised" License
4 stars 1 forks source link

updates for airs control in opsinputs #141

Closed brettcandy closed 1 year ago

brettcandy commented 1 year ago

To complete JOPA processing of AIRS the control files for cx and varobs generation need to be added to develop. These are read in during JOPA processing. They are identical to IASI and so no new ctests need to be added.

brettcandy commented 1 year ago

A successful test of using these new files in sith has been carried out. Investigation of the varobs output (via uvea) Show the following variables in the varobs file

Varobs dictionary contains the following keys: metadata (31385, 20) BriTemp (31385, 339) Tskin (31385,) ozone (31385,) SatView (31385,) surface (31385,) SatID (31385,) SolarZenith (31385,) CloudTopP (31385,) CloudFrac (31385,) NumChans (31385,) ChanNum (31385, 324) ProcSpecEmiss (31385, 339) BiasPredictors (31385, 31) latitude (31385,) longitude (31385,)

Note that the emissivity and brightnesstemperatures are expanded by 15 (to account for the amsua data tacked onto the AIRS obs for satrad processing)

brettcandy commented 1 year ago

Is this the same list as IASI and CrIS? I was just wondering if it was worth adding a new ctests or not?

yes it is - just a copy of IASI.nl in the respective cx and varobs directories. No need for ctests i think