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.

Sign up for GitHub

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

Jump to bottom

Make option to initialize model in a year other than 1750 more robust. #5

Open
FrankErrickson opened this issue Jun 8, 2021 · 1 comment
Open

Make option to initialize model in a year other than 1750 more robust. #5

FrankErrickson opened this issue Jun 8, 2021 · 1 comment
Labels
enhancement New feature or request

Comments

@FrankErrickson
Copy link
Collaborator

Currently only supports starting in the year 1750, and user would need to create their own initial condition file in the same format as the current model input data. Sort out a way to automate this, at least for the default RCMIP scenarios.
@FrankErrickson FrankErrickson added the enhancement New feature or request label Jun 8, 2021
@lrennels
Copy link
Collaborator

lrennels commented Jun 30, 2021 •
edited
Loading

@FrankErrickson this does currently run, but I think you're saying that the results aren't correct due to initialization problems? Should we make it error when the start_year !== 1750, or further just remove the keyword arg for now? I just make it warn for now in #8

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@FrankErrickson @lrennels