-
Notifications
You must be signed in to change notification settings - Fork 119
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
set_namelist.py python script fails if first namelist variable has a null value #355
Comments
@mkavulich and @gsketefian The set_namelist.py python script was replaced with uwtools in PR #1054. A test was run using the
As noted, Adding
and the
It looks like the update from |
@MichaelLueken Yes, it's ok with me to close this issue. |
Thanks, @gsketefian! Closing this issue now. |
Original issue opened by @gsketefian migrated from regional_workflow repository: ufs-community/regional_workflow#386
I confirmed that this issue is still occurring, and updated the examples for easy replication.
Description
The
set_namelist.py
script fails if the configuration it is passed (via the-u
flag) is such that the first variable has a null value.For example, the following bash will fail:
Note that the second, third, etc variables (e.g.
fix_dir_input_grid
, which would happen if${FIXgsm}
was null) can be null; in such cases,set_namelist.py
will still succeed. It only fails if the first variable is null.Solution
A temporary fix is to place the empty value that
${fn_atm_nemsio}
represents in escaped double quotes. So the following will work:For consistency,
set_namelist.py
should be modified so that the first namelist variable can also be null, or so that all empty variables need to be placed in escaped double quotes.The text was updated successfully, but these errors were encountered: