You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If a user wants to continue a simulation at time t based on the results of a previous simulation that ended at time t, they need to use a Basin / state table with the final storages from the previous simulation. We should add an output file basin_state.arrow that contains this information.
This can then also be used in Delft-FEWS for this purpose.
If PidControl nodes are also present they should also carry over state, but this could be added later, since we don't support setting this state as input either at the moment.
The text was updated successfully, but these errors were encountered:
visr
added
the
core
Issues related to the computational core in Julia
label
Apr 4, 2024
This reverts a part of 4ff9987
On Tuesday we discussed the `basin.arrow` with @SouthEndMusic and
@Huite. A few issues/PRs will come out of this, but this already removes
the endtime, such that we don't have `missing` vertical fluxes in
`basin.arrow` anymore. The downside is that the final storage is not
currently available, but we have #1358 for that, and plan to add `dS/dt
(m3/s)` as well to be able to compute it.
If a user wants to continue a simulation at time t based on the results of a previous simulation that ended at time t, they need to use a
Basin / state
table with the final storages from the previous simulation. We should add an output filebasin_state.arrow
that contains this information.This can then also be used in Delft-FEWS for this purpose.
If PidControl nodes are also present they should also carry over state, but this could be added later, since we don't support setting this state as input either at the moment.
The text was updated successfully, but these errors were encountered: