-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
GEOS-IT 5.29.4-p3 still missing stuff (1) #215
Comments
|
|
Also included: In @GEOSgcm_App: |
Ricardo, can I add one last item to the list (it came up at our reanalysis meeting today)? 21- Add historical gmi version 7 to obsys.rc with a transition to NRT files in 20220101 BEGIN geosit_gmi_bufr => gmi.%y4%m2%d2.t%h2z.bufr |
I'll do it Amal, but it still blows my mind what GEOS IT is carrying GMI - it's assimilated, and even as passive it has questionable use ... anyway. |
Ricardo, GEOSIT is not assimilating GMI, it is to be monitored only. Also, Yanqiu and Jianjun are updating us regularly on the issues with GMI assimilation which we hope can be resolved in time for R21C. |
Still more: I forgot that Rob has a modified GEOSadas.csm in the run dir ... I have now included that in a tag. |
Amal, I know the run is not assimilating GMI - I was the one who removed the date from the 3dvar to begin with; I'm just not sure about the value of using it for monitoring but so be it ... |
I am attempting to collect all know issues in a single place. We now have emails that have talking about items that are troubled in that tag, but the emails are scattered, disconnected from each other at times, and items are redundantly numbered.
Note that addressing some of these involve changes to repos other than the GEOSadas fixture. Whenever addressed, those repos should refer to this issue in GEOSadas.
I am copying and pasting from exchanges w/ Rob.
same as 16
I see inconsistencies in the gocart settings that I thought we had handled in the tag
same as 13
I see inconsistencies in the gaas obsys file that I thought we had resolved
I see a change in the obsys.rc that I don’t understand associate w/ AMSRE
??
??
??
Fixed a problem in silo.arc and mstorage.arc:
${PESTOROOT}%s/other/Y%y4/M%m2/%s.ctm_tavg_1hr_glo_C180x180x6_v72.%y4-%m2-%d2T%h2%n2Z.nc4
. ${PESTOROOT}%s/other/Y%y4/M%m2/%s.ctm_inst_1hr_glo_C180x180x6_v72.%y4-%m2-%d2T%h2%n2Z.nc4
Correct AOD_OBSCLASS in FVDAS_Run_Config to add: patmosx_ods,mod04_061_his,myd04_061_his
Correct OBSCLASS in FVDAS_Run_Config to remove geosit_wspd_pre-qc_bufr and geosit_1bssu_bufr.
Correct mhsbufr-metopc line in gsi.rc.tmpl
Modify monthly.yyyymm.pl.tmpl to remove "dastest" from the qos
Remove all C180x180x6 collections from monthly.rc16.
There were garbled lines from GIT (HEAD,develop) at the bottom of the following two files in run:
run/gmao_ozinfo.db/active.tbl
run/gmao_ozinfo.db/available.tbl
Get rid of the GIT marker lines and choose the entry that has 22 levels (for NOAA-19).
Remove AMSRE from the OBSCLASS until Jianjun figures out what is wrong.
For the LWI change in the 4 collections below (in the NOTES), LWI will only be replaced by FRACI AND for convenience, TS. Those two variables, along with the 4 other constant FRACTIONS, can be used to replace the original intent of LWI. The 4 constant variables are in the constants file (and always have been). This is a change to the tagged version of HISTORY.rc.tmpl.
Changes in HISTORY since the last test run:
The text was updated successfully, but these errors were encountered: