-
-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
♻️ refactor indexing + ✂️ decouple stride & window + ✨ support segment idxs #71
Conversation
♻️ improve output indexing
Codecov Report
@@ Coverage Diff @@
## main #71 +/- ##
==========================================
+ Coverage 97.73% 97.89% +0.16%
==========================================
Files 23 22 -1
Lines 1106 1238 +132
==========================================
+ Hits 1081 1212 +131
- Misses 25 26 +1
📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me, just need to think sometime later about the TimeSequenceStridedRolling
✨ decouple stride + support setpoints
macOS-3.10 test is failing due to problems with installing matrixprofile blue-yonder/tsfresh#937 |
is this ready for a re-review? @jvdd |
Waiting for this awesome PR to be merged! A lot of cool stuff! |
Tests on windows are failing bc poetry installation issue snok/install-poetry#94 |
♻️ Refactor indexing
vectorized=True
for strided rollinginclude_final_window
argument to FeatureCollection.calculate
(& StridedRolling)=> Decided to not do this in this PR. We will leave this for another PR.
window_idx
argument inFeatureCollection.calculate
to"end"
✂️ Decouple stride
We (@jonasvdd, @emield12, and @jvdd) believe that the stride should not be hardly coupled with a
FeatureDescriptor
. Therefore, to make tsflex more flexible (:wink:) we make the stride argument optional forFeatureDescriptor
andMultipleFeatureDescriptor
and add the functionality to pass your stride(s) to theFeatureCollection.calculate
method.FeatureDescriptor
FeatureCollection.calculate
FeatureDescriptor
/FeatureCollection.calculate
should accept multiple stridesStridedRolling
should accept multiple stridesstride
->strides
: which is either a list of stride sizes (float or pd.Timedelta) or None (inStridedRolling
andStridedRollingFactory
)StridedRolling
search sortedTODO: moet geoptimaliseerd worden
✨ Support setpoints
=> Note: we allow setpoints of different timezones as the
np.datetime64
conversion of these allow comparison..=> Decided to not do this! (as this is somewhat an ambiguous operation)
As using segment indexes is already an advanced operation, it is the user its responsability to either trim the segmented indexes or make their features robust.
🙈 other stuff
features.logger
that does not handle numeric window & strides_parse_logging_execution_to_df
RuntimeWarining
when the data its index (passed toFeatureCollection.calculate
) is not monotonically increasing