-
Notifications
You must be signed in to change notification settings - Fork 180
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
Enable ESMF threading in the ufs-weather-model forecast #1371
Changes from 11 commits
0453d5d
d904cc9
0ade235
5c1e48b
9ba87a8
67b2760
435879b
27bc311
6c5ef9f
e6865cf
c796911
2a2b4a5
a2874b2
3690332
7b483c2
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -15,6 +15,7 @@ min_seaice="1.0e-6" | |
use_cice_alb=".true." | ||
|
||
# config.ufs # TODO: This is hard-wired for P8 and needs to be refactored. For now, use case C384 | ||
# TODO: Q. for @jessicameixner-noaa: can we make these defaults in config.ufs for C384? | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. To me, this is mostly for the commented out: There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Please follow: layout_x < layout_y. Also I am not sure how the WRTTASK_PER_GROUP_GFS=86 is coming out, it may be related to taking whole nodes, but it is really machine dependent, the number may not be good for wcoss2. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Thanks @JessicaMeixner-NOAA
I am inclined to remove these as they are not wildly different than the ones in |
||
case "${CASE}" in | ||
"C384") | ||
DELTIM=300 | ||
|
@@ -26,11 +27,9 @@ case "${CASE}" in | |
#layout_x_gfs=24 | ||
#layout_y_gfs=16 | ||
#WRTTASK_PER_GROUP_GFS=86 | ||
WRTIOBUF="32M" # TODO: This value is for P8 w/ C384. Why not update/set this as default in config.fv3 C384? | ||
MEDPETS=300 # TODO: Use 300 instead of ATMPETS = layout_x * layout_y * 6 | ||
;; | ||
"C768") | ||
MEDPETS=300 | ||
*) # All other ${CASE} | ||
echo "config.defaults.s2sw: Using default settings for CASE=${CASE}" | ||
;; | ||
esac | ||
|
||
|
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.
If this is a long-term solution, I think we're going to need to copy these modulefiles to our top level in
link_workflow.sh
to satisfy NCO.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.
This is not a long term solution, but is needed ATM.
We can no longer delay the job-specific loading of the modules. The JEDI team has its own
load_ufsda_modules.sh
as a workaround, but IMO, a better more sound solution needs to be developed.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.
I think it might be good to give each job/task flexibility to load its own modules. This will allow smooth transition to new libraries to all the workflow components during development stage. Maybe we can have a unified version for opn implementation tags when the code is frozen.
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.
It appears that just loading the modules from ufs-weather-model modulefile is not enough for wcoss2.
wcoss2 also requires
cray-pals
that loads thempiexec
.This module is loaded in the run script of the regression test
https://github.com/ufs-community/ufs-weather-model/blob/495c5fd106ff3facb5b4aedbf94f8bba6c1da091/tests/fv3_conf/fv3_qsub.IN_wcoss2#LL20-L20C22
Pity!
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 Can we load
cray-pals
in https://github.com/ufs-community/ufs-weather-model/blob/develop/modulefiles/ufs_wcoss2.intel.lua?It will save us a mountain of trouble till we have a proper solution?
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.
Yes, we can. This will require model version change, I will submit a PR to see if we can get it in as soon as possible.
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.
Thank you @junwang-noaa. We will proceed w/ the hack we have for now.
Let us know when there is an update in the model hash.