-
Notifications
You must be signed in to change notification settings - Fork 210
Link staged GSI fix files instead of cloning them from gerrit #1132
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
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 |
|---|---|---|
|
|
@@ -27,7 +27,7 @@ OPTIND=1 | |
| while getopts ":ho" option; do | ||
| case "${option}" in | ||
| h) usage ;; | ||
| o) | ||
| o) | ||
| echo "-o option received, configuring for NCO" | ||
| RUN_ENVIR="nco";; | ||
| :) | ||
|
|
@@ -91,6 +91,7 @@ for dir in aer \ | |
| cpl \ | ||
| datm \ | ||
| gldas \ | ||
| gsi \ | ||
|
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. How do we handle the case that a developer does NOT want to use the staged GSI fix files? This question actually applies to all the staged fix files. One answer is that we assume the developer knows what (s)he wants to do and manually makes the required changes.
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. Since all that is being done is creating symlinks, it is a simple matter to replace one of them with a location of your choice manually afterwards.
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. Agreed. It is simple to replace one link with another. Does the g-w wiki capture this detail? Not everyone understands what these scripts do or how they work. |
||
| lut \ | ||
| mom6 \ | ||
| orog \ | ||
|
|
@@ -108,6 +109,7 @@ for dir in aer \ | |
| ${LINK} "${FIX_DIR}/${dir}/${!fix_ver}" "${dir}" | ||
| done | ||
|
|
||
|
|
||
| if [[ -d "${script_dir}/ufs_utils.fd" ]]; then | ||
| cd "${script_dir}/ufs_utils.fd/fix" || exit 1 | ||
| ./link_fixdirs.sh "${RUN_ENVIR}" "${machine}" 2> /dev/null | ||
|
|
@@ -163,15 +165,6 @@ if [[ -d "${script_dir}/gfs_wafs.fd" ]]; then | |
| fi | ||
|
|
||
|
|
||
| #------------------------------ | ||
|
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. Same question as above. What happens when a developer does NOT want to use staged GSI fix files? It may be too cumbersome to have the checkout and link script cover all possibilities. Perhaps it is sufficient to update the g-w wiki to explain options. |
||
| #--add GSI fix directory | ||
| #------------------------------ | ||
| if [[ -d "${script_dir}/gsi_enkf.fd" ]]; then | ||
| cd "${top_dir}/fix" || exit 1 | ||
| [[ -d gsi ]] && rm -rf gsi | ||
| ${LINK} "${script_dir}/gsi_enkf.fd/fix" gsi | ||
| fi | ||
|
|
||
| #------------------------------ | ||
| #--add GDASApp fix directory | ||
| #------------------------------ | ||
|
|
||
Uh oh!
There was an error while loading. Please reload this page.