-
Notifications
You must be signed in to change notification settings - Fork 163
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
Move unused ccpp suites to 'suites_not_used' directory #665
Move unused ccpp suites to 'suites_not_used' directory #665
Conversation
@grantfirl can you review on this pr to move unused suites to separate directory? |
Moving old and unused suites to separate directory makes a sense. Please, go ahead to review review comments. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Seems fine to me. The reason to move them instead of remove them entirely is because someone might be using them for research, etc. that we're unaware of?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
good practice
Testing on #1793 has completed, please go ahead and finalize reviews/approvals and begin the merging process for this PR @BrianCurtis-NOAA @junwang-noaa |
Move unused ccpp suites to suites_not_used directory (NOAA-EMC#665)
Revert "Move unused ccpp suites to suites_not_used directory (NOAA-EMC#665)"
Description
This PR moves all unused ccpp suite definition files to a separate directory (suites_not_used)
Is a change of answers expected from this PR? No.
Issue(s) addressed
Link the issues to be closed with this PR, whether in this repository, or in another repository.
(Remember, issues should always be created before starting work on a PR branch!)
Testing
How were these changes tested? Regression test on Hera
What compilers / HPCs was it tested with? Intel and gnu
Are the changes covered by regression tests? (If not, why? Do new tests need to be added?)
Have the ufs-weather-model regression test been run? Yes
On what platform? Hera
Dependencies
If testing this branch requires non-default branches in other repositories, list them.
Those branches should have matching names (ideally)
Do PRs in upstream repositories need to be merged first? No