-
Notifications
You must be signed in to change notification settings - Fork 2
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
Changes the internal behavior of TimeVaryingInputs23D to use dates rather than seconds since start date #147
base: main
Are you sure you want to change the base?
Conversation
85f2de7
to
fd40236
Compare
799cde3
to
1f95510
Compare
I am running the nightly build locally on the main branch and it is stuck after finishing the DataStructures tests. I think it have to do something with NCDatasets.jl? |
ext/TimeVaryingInputsExt.jl
Outdated
TimeVaryingInputs.evaluate!( | ||
dest, | ||
itp, | ||
Dates.Millisecond(round(Int64, 1000 * time)) + |
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.
Do you need to specify Int64
?
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.
I don't think so. I just got rid of it.
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!
I left just one question on the rounding
TVI23D stands for TimeVaryingInput23D.
TVILPF stands for time varying inputs linear period filling.
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!
closes #146 - This commit changes the internal behavior of TimeVaryingInputs23D to use dates rather than seconds since start date. This will make the transition to ITime a little easier since it is easy to convert a ITime to a date.
The behavior of TimeVaryingInputs23D will only differ when
dt
in milliseconds is an odd number or precision more than one millisecond is required. For the first case, this is because the code computesdt / 2
in_time_range_dt_dt_e
. In all other cases, the behavior should be identical as before.