-
Notifications
You must be signed in to change notification settings - Fork 52
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
Removed errorOnMissing
and endYear = end
config options
#991
Conversation
We always want an error on missing data
@cbegeman and @milenaveneziani, please let me know if you agree that these are options we no longer want to support. I was trying to fix |
Results are unpredictable and this option causes more trouble for development than it is worth.
78686de
to
00a3101
Compare
00a3101
to
10dd8de
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@xylar Yes, this change seems reasonable to me. I have rebased my branch on this one and it runs without error when endYear != end. Thanks!
Thanks @cbegeman! |
@milenaveneziani, do you have time to look this over and let me know if you're okay with it? |
oops, sorry @xylar that I missed this! |
No worries, thanks @milenaveneziani ! |
This merge removes the config option
errorOnMissing
from the[input]
section. In practice, we always want an error on missing data, rather than simply providing a warning using available data.This merge also drops support for the
end
value forendYear
. For developers,end
has been more difficult to support than it is worth. For users, it isn't a great idea to have the same analysis run produce different results depending on how far along a simulation is. In practice, we always want to run fresh analysis when we want a longer time series.