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

Need to specify simulation starting datetime for continue run? #455

Open
nmizukami opened this issue Feb 20, 2024 · 2 comments
Open

Need to specify simulation starting datetime for continue run? #455

nmizukami opened this issue Feb 20, 2024 · 2 comments
Assignees
Labels
question standalone For stand-alone run

Comments

@nmizukami
Copy link
Collaborator

nmizukami commented Feb 20, 2024

It seems like simulation start time (simStart) needs to be specified for continue run for standalone run. This is to read runoff input at correct time. Similarly, restart file the needs to be specified in fname_state_in in control file.

For cesm coupled run, the simulation start time is coming from the coupler, so it is ok. and fname_state_in is read in from rpointer file.

Erik (@ekluzek), do you think it is better to have the code figure out start time for continue run?

@nmizukami nmizukami added question standalone For stand-alone run labels Feb 20, 2024
@ekluzek
Copy link
Collaborator

ekluzek commented Apr 10, 2024

To have the code figure out the start time for a continue run, you'll need to add some similar infrastructure as in CESM to handle this. I think it is worthwhile, but might take some effort. I suppose maybe the easiest/best thing to do would be to use the CESM restart infrastructure for both cesm-coupled and standalone. It would take some work to figure it out, but then it would be something that's the same between standalone and coupled and that would be a good thing.

@nmizukami nmizukami self-assigned this Sep 4, 2024
@nmizukami
Copy link
Collaborator Author

nmizukami commented Sep 5, 2024

Just looking into the codes, fixing this needs some moving around of several subroutines, sosimStart and fname_state_in are populated accordingly from rpointer file (and restart file to get simStart information)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question standalone For stand-alone run
Projects
None yet
Development

No branches or pull requests

2 participants