-
Notifications
You must be signed in to change notification settings - Fork 177
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
Make necessary bugfixes to get aerosol cycling going #1349
Changes from all commits
e5414cf
9aaad8d
a1276d1
931ced7
6e1d5cd
9684a17
8a0603e
dbbb00c
50eb5f6
ec3ea2c
d4071bf
cd6b813
8162401
9f158f4
df40125
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 |
---|---|---|
@@ -1 +1 @@ | ||
['dust1', 'dust2', 'dust3', 'dust4', 'dust5', 'seas1', 'seas2', 'seas3', 'seas4', 'so4', 'oc1', 'oc2', 'bc1', 'bc2'] | ||
incvars: ['dust1', 'dust2', 'dust3', 'dust4', 'dust5', 'seas1', 'seas2', 'seas3', 'seas4', 'so4', 'oc1', 'oc2', 'bc1', 'bc2'] |
Original file line number | Diff line number | Diff line change | ||
---|---|---|---|---|
|
@@ -53,6 +53,14 @@ elif [[ -d /scratch1 ]] ; then | |||
module load prod_util | ||||
elif [[ -d /work ]] ; then | ||||
# We are on MSU Orion | ||||
# prod_util stuff, find a better solution later... | ||||
#module use /apps/contrib/NCEP/hpc-stack/libs/hpc-stack/modulefiles/compiler/intel/2022.1.2/ | ||||
#module load prod_util | ||||
export UTILROOT=/work2/noaa/da/python/opt/intel-2022.1.2/prod_util/1.2.2 | ||||
export MDATE=/work2/noaa/da/python/opt/intel-2022.1.2/prod_util/1.2.2/bin/mdate | ||||
export NDATE=/work2/noaa/da/python/opt/intel-2022.1.2/prod_util/1.2.2/bin/ndate | ||||
export NHOUR=/work2/noaa/da/python/opt/intel-2022.1.2/prod_util/1.2.2/bin/nhour | ||||
export FSYNC=/work2/noaa/da/python/opt/intel-2022.1.2/prod_util/1.2.2/bin/fsync_file | ||||
Comment on lines
+60
to
+63
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. May I ask what is using this? 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. Good question, there were things that were failing due to
and I just defined everyting in the prod_util module for completeness sake 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. Why can't we just add prod_util to the UFSDA stack? 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. We could, but it is maintained by JCSDA (Dom) and probably isn't worth it? Would there be a need to include these tools in the workflow scripts before JEDI is on WCOSS2? |
||||
module load "${MODS}/orion" | ||||
if [[ "${DEBUG_WORKFLOW:-NO}" == "YES" ]] ; then | ||||
module list | ||||
|
@@ -62,9 +70,6 @@ elif [[ -d /work ]] ; then | |||
ncdump=$( which ncdump ) | ||||
NETCDF=$( echo "${ncdump}" | cut -d " " -f 3 ) | ||||
export NETCDF | ||||
# prod_util stuff, find a better solution later... | ||||
module use /apps/contrib/NCEP/hpc-stack/libs/hpc-stack/modulefiles/compiler/intel/2022.1.2/ | ||||
module load prod_util | ||||
elif [[ -d /glade ]] ; then | ||||
# We are on NCAR Yellowstone | ||||
echo WARNING: UFSDA NOT SUPPORTED ON THIS PLATFORM | ||||
|
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.
Any estimate from the hpc-stack team when this problem will be resolved? It would be nice to remove this hack sooner rather than later.
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.
agreed, it's not likely to happen until the UFS spack-stack and the JEDI spack-stack are one and the same...
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. Thanks for the timing sequence.
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.
The stack unification will take a while till the GSI and GDASApp can be built and run w/ the same compiler version.