-
Notifications
You must be signed in to change notification settings - Fork 253
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 CDEPS submodule and CDEPS tests #599
Update CDEPS submodule and CDEPS tests #599
Conversation
* Change application name "DATM" to "NG-GODAS" * Change application name "DATM-NEMS" to "NG-GODAS-NEMSDATM" * Use a mesh file in MOM6 cap instead of a grid file
@binli2337 please bring these up to date with respective authoritative repositories
|
@binli2337 Please add a fix to the rt_35d.conf. The first compile line is commented out but please add it there too. Add a comma between the two suite file names:
|
@binli2337 please bring these up to date with respective authoritative repositories
|
@binli2337 New baseline (develop-20210526) is ready on Cheyenne. |
add RegressionTests_hera.gnu.log add RegressionTests_wcoss_cray.log
@binli2337 please bring these up to date with respective authoritative repositories
|
@binli2337 please bring these up to date with respective authoritative repositories
|
The github-actions repo-check error seen above is due to the new CDEPS submodule pointing to develop. This issue need to be fixed after this PR commits. |
tests/compile.sh
Outdated
|
||
if [[ "${MAKE_OPT}" == *"APP=DATM_NEMS"* ]]; then | ||
CMAKE_FLAGS="${CMAKE_FLAGS} -DAPP=DATM_NEMS" | ||
#if [[ "${MAKE_OPT}" == *"APP=DATM"* ]]; then |
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.
Can we remove the commented lines 152-154 and 159-161 ?
@@ -16,7 +16,7 @@ list(APPEND CMAKE_MODULE_PATH ${CMAKE_SOURCE_DIR}/CMakeModules/Modules) | |||
############################################################################### | |||
|
|||
# Valid applications and choices | |||
list(APPEND VALID_APPS ATM ATMW S2S S2SW DATM DATM_NEMS) | |||
list(APPEND VALID_APPS ATM ATMW S2S S2SW NG-GODAS NG-GODAS-NEMSDATM) |
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.
No changes have been made in the NEMS driver to switch these names---it will still use "FRONT_NEMS_DATM" and "FRONT_CDEPS_DATM" which then asks for "model" names nems_datm
or datm
. It seems we're introducing a lot of inconsistency.
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.
@DeniseWorthen You are correct.
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.
@DeniseWorthen My understanding is that this is actually to avoid confusion. in NEMS driver we specify the subcomponent models, not the applications names. Using DATM or NEMS_DATM for both subcomponent and application names could be confusing. Here the NG_GODAS is application name, this application will still define the subcomponents DATM (cdeps datm), MOM6 and CICE6 etc. While before we use DATM as application name and use DATM also as DATM subcomponent along with other subcomponents.
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.
Are both NG-GODAS
and NG-GODAS-NEMSDATM
needed? What's the difference?
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.
NG-GODAS refers to "mom6_cice6_cdeps_datm" application.
NG-GODAS-NEMSDATM refers to "mom_6_cice6_nems_datm" application.
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.
OK. But do we need both? Didn't we switch to CDEPS, why do we need nems? Are the results different when CDEPS is used compared to NEMS? Are different atm data used?
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.
In the future, NEMS_DATM will be removed from ufs-weather-model. See a related issue at #565.
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.
@junwang-noaa I see, thanks. I do see how DATM is being used two ways (app and component) so this is probably better.
@binli2337 please bring these up to date with respective authoritative repositories
|
Since actions thinks the cdeps is not up to date, tests do not run. I suggest we skip it for this PR. |
@MinsukJi-NOAA OK. |
@binli2337 please bring these up to date with respective authoritative repositories
|
@binli2337 There could be an issue in this naming convention ( |
@binli2337 maybe it has issue if you have |
@binli2337 i checked it with |
Here is the proposed solution for
So, order of APP definition does not affect the results and it match always the correct one. I'll push this changes into my HAFS CDEPS branch that could god eventually to upstream repository.
|
|
@climbfuji The build add more APP names to CMAKE_FLAGS even if you only provide APP option without CCPP and STATIC ones. So, even for it, we still need fix. |
I was only commenting on |
…-community#599) * Improve radiative fluxes and cloud cover in ccpp/physics for HR1
PR Checklist
Ths PR is up-to-date with the top of all sub-component repositories except for those sub-components which are the subject of this PR. Please consult the ufs-weather-model wiki if you are unsure how to do this.
This PR has been tested using a branch which is up-to-date with the top of all sub-component repositories except for those sub-components which are the subject of this PR
An Issue describing the work contained in this PR has been created either in the subcomponent(s) or in the ufs-weather-model. The Issue should be created in the repository that is most relevant to the changes in contained in the PR. The Issue and the dependent sub-component PR
are specified below.
If new or updated input data is required by this PR, it is clearly stated in the text of the PR.
Instructions: All subsequent sections of text should be filled in as appropriate.
The information provided below allows the code managers to understand the changes relevant to this PR, whether those changes are in the ufs-weather-model repository or in a subcomponent repository. Ufs-weather-model code managers will use the information provided to add any applicable labels, assign reviewers and place it in the Commit Queue. Once the PR is in the Commit Queue, it is the PR owner's responsiblity to keep the PR up-to-date with the develop branch of ufs-weather-model.
Description
Issue(s) addressed
Link the issues to be closed with this PR, whether in this repository, or in another repository.
(Remember, issues must always be created before starting work on a PR branch!)
Testing
How were these changes tested? What compilers / HPCs was it tested with? Are the changes covered by regression tests? (If not, why? Do new tests need to be added?) Have regression tests and unit tests (utests) been run? On which platforms and with which compilers? (Note that unit tests can only be run on tier-1 platforms)
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?
If so add the "waiting for other repos" label and list the upstream PRs