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
Can pytimetk be augmented to support multi-index columns?
The pytimetk augment_* API appears to makes the assumption that columns are single indexes i.e. multi-index not supported.
In the augment_* functions, the date and value columns parameters make these assumptions, but if i had a situation where i had a multi-index, i would need to collapse the multi-index down into a single dimension before i can utilize pytimetk.
Here's an example. The pool forms a 2nd dimension on the column multi-index. this allows the rows to be keyed by dates only along the rows (i.e. longitudinally).
In pandas, this is also the ideal format to perform dataset-wide window operations. It preserves the dimensionality of the columns as well. This way we can stack / unstack the original columns into rows if we want to preserve the inbound dimensionality.
Assuming a singular dimension is a limiting factor for more advanced cases beyond more simple datasets / use cases.
Would like to hear any thoughts on this - most datasets I imagine are multi-dimensional / have multiple attributes. Thanks.
The text was updated successfully, but these errors were encountered:
Can pytimetk be augmented to support multi-index columns?
The pytimetk augment_* API appears to makes the assumption that columns are single indexes i.e. multi-index not supported.
In the
augment_*
functions, the date and value columns parameters make these assumptions, but if i had a situation where i had a multi-index, i would need to collapse the multi-index down into a single dimension before i can utilize pytimetk.Here's an example. The pool forms a 2nd dimension on the column multi-index. this allows the rows to be keyed by dates only along the rows (i.e. longitudinally).
In pandas, this is also the ideal format to perform dataset-wide window operations. It preserves the dimensionality of the columns as well. This way we can stack / unstack the original columns into rows if we want to preserve the inbound dimensionality.
Assuming a singular dimension is a limiting factor for more advanced cases beyond more simple datasets / use cases.
Would like to hear any thoughts on this - most datasets I imagine are multi-dimensional / have multiple attributes. Thanks.
The text was updated successfully, but these errors were encountered: