Skip to content
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

Update crtm fix in UFS DA atmospheric analysis scripts #1110

Closed
RussTreadon-NOAA opened this issue Nov 7, 2022 · 1 comment · Fixed by #1111
Closed

Update crtm fix in UFS DA atmospheric analysis scripts #1110

RussTreadon-NOAA opened this issue Nov 7, 2022 · 1 comment · Fixed by #1111
Assignees

Comments

@RussTreadon-NOAA
Copy link
Contributor

Description
UFS DA unified forward operator validation uses CRTM coefficients from crtm/2.3.0 The g-w UFS DA variational and ensemble analysis scripts use crtm/2.3.0_jedi. This is not correct.

Requirements
Replace references to crtm/2.3.0_jedi with crtm/2.3.0 in exgdas_global_atmos_analysis_run.sh and exgdas_global_atmos_ensanal_run.sh

Dependencies
None.

@RussTreadon-NOAA
Copy link
Contributor Author

Work for this issue will be done in g-w branch feature/ufsda_crtm

@RussTreadon-NOAA RussTreadon-NOAA self-assigned this Nov 7, 2022
WalterKolczynski-NOAA pushed a commit that referenced this issue Nov 10, 2022
UFS DA unified forward operator (UFO) validation uses `crtm/2.3.0` for radiances.     UFS DA scripts which exercise UFO for radiance assimilation should use the same CRTM coefficients.   UFS DA scripts `exgdas_global_atmos_analysis_run.sh` and `exgdas_global_atmos_ensanal_run.sh` currently use CRTM coefficients from `crtm/2.3.0_jedi`.   This is not correct. 

The CRTM coefficient path for the two UFS DA analysis scripts in question has been updated in [`feature/ufsda_crtm`.](https://github.com/NOAA-EMC/global-workflow/tree/feature/ufsda_crtm)

Fixes #1110
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant