Replies: 1 comment 3 replies
-
Had we done the cutting into windows eagerly, you'd just pay the same price but at the time of calling Can you share a bit more about what are you trying to do? I'm not sure what to advise you without more context. |
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Is this necessary to return a Lazy CutSet instead of an eager one? My use case is cutting a cutset into windows and then using
PrecomputedFeatures()
to load features. ButPrecomputedFeatures()
cannot take lazy cutset, so I had to convert the set to eager again, which caused computation overhead.So essentially this is like: eager ->
cut_into_windows()
-> lazy ->to_eager()
-> eager ->PrecomputedFeatures()
Just timed it,
to_eager()
almost takes half of the time in each data loading round.Is there a better way to do this?
Beta Was this translation helpful? Give feedback.
All reactions