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

Transfer atmospheric observation test YAMLs to JCB framework #24

Open
18 tasks
ADCollard opened this issue Aug 19, 2024 · 0 comments
Open
18 tasks

Transfer atmospheric observation test YAMLs to JCB framework #24

ADCollard opened this issue Aug 19, 2024 · 0 comments

Comments

@ADCollard
Copy link

When JCB was introduced in GDASApp, the yamls in parm/atm/obs/config were converted but the files in parm/atm/obs/testing did not make it. The last commit with the testing directory was 05bb64157d36619ea3f5216245ba9adccbeafc51.

We need to transfer the outstanding YAMLs from the testing directory to the JCB framework in this repository.

This will be a three step process.

  1. Ensure that the ush/ufoeval/run_ufo_hofx_test.sh script will complete with the converted yaml.
  2. Ensure that the HofX, QC and observation errors are reproducible in the GSI geovals context using ush/ufoeval/run_ufo_hofx_test.sh. Set passed Benchmark values accordingly.
  3. Make modifications for end-to-end testing and validate (including but not limited to including thinning).

Checklist. Step 1:

  • amsua_metop-a/b/c
  • amsua_n15/n18/n19
  • avhrr_metop-a/b
  • avhrr_n18/n19
  • mhs_metop-b/n19
  • seviri_m08/m11

Checklist. Step 2:

  • amsua_metop-a/b/c
  • amsua_n15/n18/n19
  • avhrr_metop-a/b
  • avhrr_n18/n19
  • mhs_metop-b/n19
  • seviri_m08/m11

Checklist. Step 3:

  • amsua_metop-a/b/c
  • amsua_n15/n18/n19
  • avhrr_metop-a/b
  • avhrr_n18/n19
  • mhs_metop-b/n19
  • seviri_m08/m11

This should be complementary to the sanity checks in GDASApp Issue 1240

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

No branches or pull requests

1 participant