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

Introducing ATOMIC test case #564

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Introducing ATOMIC test case #564

wants to merge 1 commit into from

Conversation

ihursmas
Copy link

@ihursmas ihursmas commented Mar 4, 2025

This pull request introduces forcing and namelists associated with the ATOMIC field campaign. Specifically:

  • Adding DEPHY-format associated case configuration namelist files, which will be named as atomic_[period].nml, into scm/etc/case_config/. There are seven periods in total.
  • Adding suite_SCM_GFS_v17_p8_ugwpv1_no_nsst.xml and suite_SCM_RRFS_v1beta_no_nsst.xml into ccpp/suites/. This change allows the ATOMIC test case to be run using the 'sfc_ocean' scheme (instead of 'nsst'), which may work more properly for the oceanic field campaign cases (as suggested by Issue #518).
  • Modifying suite_info.py in scm/src/ and rt_test_cases.py in test/ accordingly. These changes enable the CCPP SCM to run the SCM_GFS_v16_no_nsst, SCM_GFS_v17_p8_ugwpv1_no_nsst, and SCM_RRFS_v1beta_no_nsst suites.

@ihursmas ihursmas changed the title Introduce ATOMIC test case Introducing ATOMIC test case Mar 4, 2025
@hertneky
Copy link
Collaborator

hertneky commented Mar 4, 2025

@ihursmas Thanks for the contribution. I will try to get to this within the next week.

@grantfirl
Copy link
Collaborator

@ihursmas I've updated the v7.0 release asset for the processed_case_input directory to include your new case files. You can test is by re-running ./contrib/get_all_static_data.sh if you'd like.

@ihursmas
Copy link
Author

ihursmas commented Mar 5, 2025

@grantfirl and @hertneky Thank you for working on this together!

I tried ./contrib/get_all_static_data.sh, which successfully gets the ATOMIC forcing data under processed_cae_input. Not sure if the permission of these file would matter though; other forcing files seem to have 644 (I set the permission of these files to be 755 in /home/I-kuan.Hu/ATOMICforcings/ for better accessibility).

@hertneky
Copy link
Collaborator

hertneky commented Mar 5, 2025

Note to self: Add to UG

@ihursmas Can you provide bullets on the cases - some info to add to section 7.2 of UG?

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 this pull request may close these issues.

3 participants