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
Does not allow one component to share time series data across two fields (e.g., active power and reactive power).
Does not allow one component to share time series data with different initial times.
The user can accidentally store the same time array data multiple times.
Dan and Pedro brainstormed a solution.
Create this new class:
class ProfileData(BaseModel):
data: pa.Array | BaseQuantity
hash_str: str
SingleTimeSeries would store it instead of the same data type above. The profile data would get serialized with its hash instead of the currently-used UUID. Duplicate data would never be stored.
The user does not have to know about the ProfileData class. It can get created automatically in System.add_time_series. The user interfaces stay the same. There is one new user pattern to share time series:
# ts1 is a SingleTimeSeries that is already stored in the system.
ts2 = SingleTimeSeries.from_existing(ts1, variable_name=X, initial_time=Y, resolution=Z)
The text was updated successfully, but these errors were encountered:
Problems with the current design of time series:
Dan and Pedro brainstormed a solution.
Create this new class:
SingleTimeSeries would store it instead of the same data type above. The profile data would get serialized with its hash instead of the currently-used UUID. Duplicate data would never be stored.
The user does not have to know about the ProfileData class. It can get created automatically in
System.add_time_series
. The user interfaces stay the same. There is one new user pattern to share time series:The text was updated successfully, but these errors were encountered: