-
Notifications
You must be signed in to change notification settings - Fork 107
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
Removal of ds
from the forcing file(s)
#556
Comments
Great. This has been an outstanding issue since the start of summa.
I think the existence of ds was a convenience for certain plotting
routines, but is redundant and needlessly complicates the forcing files, as
it can be directly assigned (no inference needed) from the forcing
timestamp.
I wrote code years ago to do this but it got lost in some reorganized/split
PRs.
Don't add a control file setting (again, redundant) -- infer from the
forcing files, which is naturally backward compatible.
Defined timestep may also be in the initial state files, but is more
complicated to remove given how early they're read. Next target, perhaps.
Thanks, I'm very glad to see it dealt with.
…On Mon, Feb 12, 2024 at 2:42 PM Shervan Gharari ***@***.***> wrote:
Feature Requests
- Removal of ds or time step of the forcing (in second) from the
forcing file.
- Currently, the ds should be added to forcing files. Removal of ds
and adding it to the control file or inferring it internally will reduce
the workflow to prepare the forcing for SUMMA.
- Will the proposed feature be backward compatible? (1) Earlier setup
should not fail if variable ds is inferred by SUMMA internally. (2)
However, if implemented in the control file, the time step should be added
to an existing setup.
- Will the proposed feature change the science results of SUMMA? No,
it reduces the workflow to prepare the forcing files.
- The inference of ds is done internally for cesm-coupling branch of
mizuRoute in the standalone folder in case that is helpful.
Thank you in advance and let me know if I can assist in any form.
—
Reply to this email directly, view it on GitHub
<#556>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABIKARNBKRCVV2NJG24GF23YTKEFPAVCNFSM6AAAAABDFN42JOVHI2DSMVQWIX3LMV43ASLTON2WKOZSGEZTCMBTGQ3DCNY>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Feature Requests
ds
or time step of the forcing (in second) from the forcing file.ds
should be added to forcing files. Removal ofds
and adding it to the control file or inferring it internally will reduce the workflow to prepare the forcing for SUMMA.ds
is inferred by SUMMA internally. (2) However, if implemented in the control file, the time step should be added to an existing setup.ds
is done internally forcesm-coupling
branch ofmizuRoute
in thestandalone
folder in case that is helpful.Thank you in advance and let me know if I can assist in any form.
The text was updated successfully, but these errors were encountered: