-
Notifications
You must be signed in to change notification settings - Fork 1
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
Consider time-dependent processes #79
Comments
Example processes that depend on time: For TSM - these seem to assume a timestep of 1 second: https://github.com/EcohydrologyTeam/ClearWater-modules/blob/main/src/clearwater_modules/tsm/processes.py
For NSM, time dependent processes have a timestep variable, which is, by default, 1.
|
@imscw95 @kewalak @aufdenkampe, I'm going to work on resolving this NSM: Looking at the state variables and time-dependent processes (e.g., Ap) in NSM, it looks like it's currently set with units equal to 1 day and passing all tests. TSM:
Seems like we'll want to align Thanks! |
Hey @sjordan29. It'll definitely be easier to convert the TSM units from seconds to days just thinking about the amount of variables/coefficients we'd need to convert. Also, I'd think modeling these processes at the seconds scale is overkill. Days is probably too coarse for temperature though cause of daily cycles, so if we want them aligned at a useful timescale, we'd probably need to change the NSM units, which would be a major undertaking. Is having them on different time scales feasible? I think hours is the ideal timescale for temp and we could probably convert that pretty easily. On the cp_water, is the temperature unit relevant, since the amount of energy to change 1 degree C vs 1 degree K would be the same right, since the two are always different by a constant value? I think the cp_water curve, which relates water temp to the cp_water value would be sensitive to the water temp unit. I did some googling and the cp_water estimates were more or less the same for both J/gC and J/gK. |
Thanks! Sounds good, I think I will work on addressing this in TSM. Since TSM is passing all tests against calculated values -- can you confirm that the comparison was done at 1 second output? We can keep the values the same even with this change, and just modify the |
Yes, confirmed that the TSM tests were for dt = 1 second. |
Considering both
tsm
andnsm
, look through variables and processes that are time-dependent and consider how the (user-defined) time dim will be used to make sure the timestep is correctly handled.As part of this issue, we should rename the
timestep
variable that's used in processes todt
to avoid confusion with the timestep incrementor.The text was updated successfully, but these errors were encountered: