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

Allow use_init_interp in a branch case even though it doesn't do anything #786

Closed
billsacks opened this issue Aug 13, 2019 · 1 comment · Fixed by #883
Closed

Allow use_init_interp in a branch case even though it doesn't do anything #786

billsacks opened this issue Aug 13, 2019 · 1 comment · Fixed by #883
Assignees
Labels
priority: high High priority task to fix soon, e.g., because it is a problem in important configurations type: enhancement new capability or improved behavior of existing capability
Milestone

Comments

@billsacks
Copy link
Member

If you try to run a branch case with use_init_interp = .true., the model dies at runtime with the message, ERROR: Can only set use_init_interp if finidat is set.

On the surface, this check that use_init_interp can only be set if finidat is set seems reasonable. However, it causes problems in practice if you set up a branch case using a compset and resolution for which use_init_interp are set automatically (via CLM_NAMELIST_OPTS) (note that that automatic setting is done in some CESM2.1 release configurations in order to have some compset/resolution combinations automatically give a hybrid case with use_init_interp = .true., to interpolate from the out-of-the-box refcase). This was a problem in the recent CESM tutorial.

We should reduce the error checking on use_init_interp, so that it can be set to .true. even if finidat is not set. In this case, it should just be ignored, and a warning message should be printed to the log file stating that we're ignoring use_init_interp in this branch run.

I reproduced this on my mac as follows:

First, I created a startup case:

./create_newcase --case /Users/sacks/projects/scratch/check_branch_baseline_0813a --compset I2000Clm50BgcCropQianRsGs --res f10_f10_musgs --run-unsupported

./xmlchange NTASKS=4
./xmlchange STOP_N=1

Then I created a branch:

./create_newcase --case /Users/sacks/projects/scratch/check_branch_0813a --compset I2000Clm50BgcCropQianRsGs --res f10_f10_musgs --run-unsupported

./xmlchange NTASKS=4
./xmlchange RUN_TYPE=branch
./xmlchange RUN_REFCASE=check_branch_baseline_0813a
./xmlchange RUN_REFDATE=2000-01-02
./xmlchange STOP_N=1
./xmlchange GET_REFCASE=FALSE
./xmlchange CLM_NAMELIST_OPTS=use_init_interp=.true.

And I prestaged the restart files from the first case into the second case's run directory.

@billsacks billsacks added type: enhancement new capability or improved behavior of existing capability priority: high High priority task to fix soon, e.g., because it is a problem in important configurations labels Aug 13, 2019
@billsacks billsacks added this to the cesm2.1.2 milestone Aug 13, 2019
@billsacks billsacks added this to To do in High priority Aug 13, 2019
@billsacks billsacks moved this from To do to Needs triage in High priority Aug 13, 2019
@ekluzek ekluzek self-assigned this Aug 13, 2019
@ekluzek ekluzek moved this from Needs triage to To do in High priority Aug 23, 2019
@ekluzek
Copy link
Contributor

ekluzek commented Nov 15, 2019

Fixed in release-clm5.0.28

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority: high High priority task to fix soon, e.g., because it is a problem in important configurations type: enhancement new capability or improved behavior of existing capability
Projects
Development

Successfully merging a pull request may close this issue.

2 participants