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
We currently support the possibility for inconsistent time series. Different lengths and initial times but same resolution across components.
This presents a problem for some simulations since we need to check the consistency of the time series across devices. We need a function that checks that all the SingleTimeSeries have the same initial time and length and also get the initial_time if they are consistent.
It might be possible to still permit inconsistent time series but requires calculating the intersection of time that is valid and that might be more cumbersome.
#255 added check_time_series_consistency for SingleTimeSeries. It will return the initial timestamp and length if all time series are consistent. Otherwise, it will throw an exception. This will likely satisfy most use cases for this request. We can leave this issue open to track the addition of determining the intersection of time series with different start and end times.
we need a method similar to
get_forecast_initial_timestamp(sys)
but for systems with onlySingleTimeSeries
The text was updated successfully, but these errors were encountered: