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
Fitting a slicer to a grouped dataset, say grouped by mode, currently makes it fail on features that have not been grouped by mode.
In a typical case, SliceIntervals obtained from some grouped Feature to be used for slicing would have the levels corpus, piece, mode, intervals. In principle, it will be possible to use Feature.apply_slice_intervals() even when a feature does not have a mode level (i.e., it hasn't been grouped by mode, e.g. because it's Notes that don't come with keys by default).
Suggested solution
Dropping the mode level from the SliceIntervals, applying it to the feature, re-adding the mode level through a join operation.
The text was updated successfully, but these errors were encountered:
johentsch
pushed a commit
to johentsch/dimcat
that referenced
this issue
Jan 16, 2024
Fitting a slicer to a grouped dataset, say grouped by mode, currently makes it fail on features that have not been grouped by mode.
In a typical case,
SliceIntervals
obtained from some grouped Feature to be used for slicing would have the levelscorpus, piece, mode, intervals
. In principle, it will be possible to useFeature.apply_slice_intervals()
even when a feature does not have amode
level (i.e., it hasn't been grouped by mode, e.g. because it'sNotes
that don't come with keys by default).Suggested solution
Dropping the
mode
level from the SliceIntervals, applying it to the feature, re-adding the mode level through a join operation.The text was updated successfully, but these errors were encountered: