-
Notifications
You must be signed in to change notification settings - Fork 163
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
add nocolons
option to namelist.wps.all_options
#96
Comments
It may have been quite some time since the |
I seem to remember that the real program may not work with the nocolons option activated, where the metgrid file has underscores instead of colons. |
|
I used the |
@andreas-h I seriously doubt that WPS in your case did not include colons in filenames. See some of the places below which unconditionally use colons. Can you name some example filenames that you got? Maybe we talk about different things. WPS/metgrid/src/write_met_module.F Lines 33 to 39 in 99f3ef5
Lines 133 to 157 in 99f3ef5
Lines 389 to 391 in 99f3ef5
|
File names look like this:
met_em.d05.2015-08-27_12_00_00.nc
Ungrib output does indeed contain colons, but as that's never being read by wrf with pnetcdf I don't mind.
|
Revisiting this request - I've found that the colons in the ungrib output is breaking my workflow when using singularity containers. The following bind statement fails - singularity tries to bind a SFCFILE file instead:
I do note that singularity v3.9 onwards might not be subject to this limitation (see sylabs/singularity#118) - but I'm stuck with singularity 3.5.2 on our local HPC system, which definitely can't cope with this issue. |
It would be nice if
nocolons
would be added to thenamelist.wps.all_options
file, in order to improve discoverability by the user.If welcome, I'm happy to submit a PR.
The text was updated successfully, but these errors were encountered: