-
Notifications
You must be signed in to change notification settings - Fork 211
Updates for HR4 tag #2914
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
Updates for HR4 tag #2914
Changes from all commits
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 | ||
|---|---|---|---|---|
|
|
@@ -31,7 +31,11 @@ local WRITE_GROUP=${WRITE_GROUP:-1} | |||
| local WRTTASK_PER_GROUP=${WRTTASK_PER_GROUP:-24} | ||||
| local ITASKS=1 | ||||
| local OUTPUT_HISTORY=${OUTPUT_HISTORY:-".true."} | ||||
| local HISTORY_FILE_ON_NATIVE_GRID=".true." | ||||
| if [[ "${DO_JEDIATMVAR:-}" == "YES" ]]; then | ||||
| local HISTORY_FILE_ON_NATIVE_GRID=".true." | ||||
| else | ||||
| local HISTORY_FILE_ON_NATIVE_GRID=".false." | ||||
|
Contributor
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. Quick question, when HISTORY_FILE_ON_NATIVE_GRID=".false.", will the softlinks cubed_sphere_grid_atmf???.nc/cubed_sphere_grid_sfcf???.nc still be created?
Contributor
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 point @junwang-noaa . @aerorahul , logic should be added to forecast_postdet.sh where those soft links are created, depending on whether JEDI is being used. Starting here: global-workflow/ush/forecast_postdet.sh Line 236 in 108db4d
Contributor
Author
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 catch @junwang-noaa
Contributor
Author
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. @DavidNew-NOAA
Contributor
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. @aerorahul Yeah, that was a mistake on my part
Contributor
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. @aerorahul Well, maybe it was more sloppiness. That |
||||
| fi | ||||
| local WRITE_DOPOST=${WRITE_DOPOST:-".false."} | ||||
| local WRITE_NSFLIP=${WRITE_NSFLIP:-".false."} | ||||
| local NUM_FILES=${NUM_FILES:-2} | ||||
|
|
||||
Uh oh!
There was an error while loading. Please reload this page.
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.
Should this be set in a config file, so that these lines in
parsing_model_configure_FV3.shbecome:local HISTORY_FILE_ON_NATIVE_GRID=${history_file_on_native_grid:-".false."}and
history_file_on_native_gridis set inconfig.ufsMaybe not, but I don't know what the design philosophy is and how all these scripts are supposed to fit together. It seems like some variables in this script are indeed coming from
config.ufs.