-
Notifications
You must be signed in to change notification settings - Fork 79
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
New unintuitive behavior for RUN_TYPE=branch simulations #525
Comments
Thank you @ekluzek for laying this out clearly. I agree that we should fix this in some way. |
A list of ideas I have:
I think most of the above should be done all at once. I'd like to hear others about setting it to UNSET. I'm thinking actually that maybe 6 is a nice simple solution to get the naive simple case to work. But, I also would like for there to be some file existence checking in place when the file is going to be used, so also do 1. |
I made an error in the setting of RUN_REFDATE, in the original post that I'm just correcting. |
… allow continue_run as well), add it as a file that will be put into cpl.input_data_list for existence checking, fixing ESCOMP#525
With the rpointer updates it's now required to set DRV_RESTART_POINTER when you do a RUN_TYPE=branch simulation in addition to other settings. The default of drv.rpointer is most likely going to be wrong for branching from a case with rpointer files with timestamps on them. Coupled with #524 this means you setup a case and don't get any clear error messaging on what's wrong.
Here's a sample case to replicate what I mean based off of using ctsm5.3.020 which has: cmeps1.0.33, ccs_config_cesm1.0.16 and cime6.1.59 (I'm using an mpi-serial single gridcell case just to make a simpler smaller test that can also be run interactively without going into the queue):
It fails at runtime because it can't find the drv.rpointer file, but the error messaging is insufficient as I say above. I have a list of ideas I'll add in the next comment.
Pinging maintainers. I know Jim will want to weigh in on this, but figure he might still be traveling so might not see this for awhile.
@briandobbins @billsacks @jedwards4b @fischer-ncar
The text was updated successfully, but these errors were encountered: