-
Notifications
You must be signed in to change notification settings - Fork 19
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
Use t_end to determine output frequency #2605
Conversation
b1cd9d9
to
926459e
Compare
This will still cause issues for the current longrun, as they are less than a year with daily output. I will get back to you with a better logic later this afternoon. |
How about: Is this too complicated? |
926459e
to
9497f90
Compare
No, easy peasy |
b416a11
to
c646272
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.
Thank you!
Just realized that some of the longruns will fail because their output changed. |
1810fe5
to
e7e4acb
Compare
The logic is as follows: If `t_end < 1 day` take hourly means, if `t_end < 30 days` take daily means, if `t_end < 120 days` take means over ten days, If `t_end >= 120 year` take monthly means.
e7e4acb
to
c693763
Compare
The logic is as follows:
If
t_end < 1 day
take hourly means,if
t_end < 1 year
take daily means,If
t_end >= 1 year
take monthly means.