-
Notifications
You must be signed in to change notification settings - Fork 150
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
Two small tweaks to thinning #734
Conversation
@ADCollard , from whom can we request peer reviews? |
ctests on hera:
In each case the only differences in the first outer loop was the ATMS statistics, as expected. After the first outer loop, the results diverged. Also as expected. |
@emilyhcliu would be the best as I already told her about this (and she agrees we need these changes!). @xincjin-NOAA, @azadeh-gh or @HaixiaLiu-NOAA would be good too. Thanks. |
Yes! @ADCollard talked to me about the two proposed changes related to thinning, and I totally agreed with them. Approved! |
WCOSS2 ctests
All three failed tests are due to differences in how ATMS radiances are assimilated. Both hafs tests see a significant increase in the number of ATMS NOAA-20 observations passing the initial QC as shown below
Comparison of the contrl and updat initial QC of ATMS radiances show that slightly fewer ATMS observations are assimilated in the updat code
|
@ADCollard : the increase in the number of assimilated ATMS observations in the hafs cases is significant. The updat code keeps 16315 ATMS observations whereas the contrl only keeps 2890. This increase is related to removal of lines 549 and 550 from
from the updat code. We do not see a similarly large increase in the number of ATMS observations kept by the updat code in the global_4denvar case. The number of ATMS observation read increases significantly but not the number kept.. The global _4denvar case has Does this explanation of the difference between hafs and global behavior make sense? I don't know if operational regional DA systems assimilate ATMS data with |
@RussTreadon-NOAA Thanks for highlighting this. I believe this difference is not related to This change should make ATMS numbers more consistent with AMSU-A. The snapshot below implies that it is a lot closer. Updat:
Control:
|
Thank you @ADCollard for explaining what's going on. |
Orion ctests
The netcdf_fv3_regional and rrfs_3denvar_glbens failures were due to the thmethresh2 check. For both tests the hiproc_updat wall time exceeded the hiproc_contrl wall time. This is not a fatal fail. The hafs and global_4denvar failures are for the same reasons as noted above. This PR alters the assimilation of ATMS data. These three tests assimilate ATMS data. These failures are expected. |
Hercules ctests
This behavior is expected and consistent with what is observed on WCOSS2 (Dogwood) and Hera. |
This PR addresses GSI #731. It modifies the satthin.F90 routine to allow data to be processed unthinned in the GSI without requiring exorbitant resources and it removes an unnecessary thinning from the read_atms.f90 routine.
The change to satthin reduces the value of
itxmax
from 1.e9 to 1.e7 which should be sufficient for most sensors. But if a larger number is required for a sensor, this may be passed in via optional argument.This change will change results for ATMS only as documented in the issue.
Checklist