Skip to content
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

Parameter file formatting has changed #2347

Closed
wwieder opened this issue Feb 5, 2024 · 3 comments · Fixed by #2350
Closed

Parameter file formatting has changed #2347

wwieder opened this issue Feb 5, 2024 · 3 comments · Fixed by #2350
Assignees
Labels
bfb bit-for-bit bug something is working incorrectly

Comments

@wwieder
Copy link
Contributor

wwieder commented Feb 5, 2024

Brief summary of bug

Changes to the formatting of the default parameter file make the file difficult to work with outside of python.

General bug information

for example, an ncdump on the new parameter file produces this:

ncdump -v bgc_rf_l1s1 /glade/campaign/cesm/cesmdata/inputdata/lnd/clm2/paramdata/ctsm51_params.c240105.nc 
bgc_rf_l1s1 = _ ;

whereas doing this for an older file shows:

ncdump -v bgc_rf_l1s1 /glade/campaign/cesm/cesmdata/inputdata/lnd/clm2/paramdata/ctsm51_params.c231117.nc 
bgc_rf_l1s1 = 0.55

Besides making it difficult to quickly query default parameter values, this bug makes modifying a parameter file as we describe on the wiki impossible. It also makes it difficult to use nco commands, like ncap2, because it's difficult to then check that modified parameter values have been changed as intended.

CTSM version you are using:
latest master tag, ctsm5.1.dev166

Does this bug cause significantly incorrect results in the model's science?
No, but it does make modifying the parameter file with ncdump or nco commands difficult

Configurations affected: [Fill this in if known.]
All

@wwieder wwieder added bug something is working incorrectly tag: simple labels Feb 5, 2024
@wwieder
Copy link
Contributor Author

wwieder commented Feb 7, 2024

note here, this would be an easy one for a bfb_dev tag, but if you can share a corrected parameter file that I can more easily edit it would be helpful, Sam.

@olyson
Copy link
Contributor

olyson commented Feb 7, 2024

Yes, I can't seem to use the approach detailed on the wiki to add a new parameter to the parameter file. I can run through the steps ok, but when I try to use the new parameter file in a simulation I get:

ERROR: ERROR: crop has wrong valuesERROR in pftconMod.F90 at line 1344

which is not something I changed. An ncdump -v crop of the file gives:

crop = 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, _, _, _, _, _, _, _, _,
_, _, _, _, _, _, _, _, _, _, _, _, _, _, _, _, _, _, _, _, _, _, _, _,
_, _, _, _, _, _, _, _, _, _, _, _, _, _, _, _, _, _, _, _, _, _, _, _,
_, _, _, _, _, _, _, _ ;

I think the "_"'s should be 1s.
I'm not sure how to resolve this so I can move forward with my deadveg PR. Suggestions?

@samsrabin
Copy link
Collaborator

@olyson I'll go ahead and make new parameter files later this afternoon.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bfb bit-for-bit bug something is working incorrectly
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants