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
With PR #408 and commit 8c88349, the data processing steps (filtering, resampling, epoching...) are done by a sklearn pipeline.
So we could use the full pipeline (procesing+classification) to create the code that identifies the pipeline in the results, instead of only the classifier.
This would allow to differentiate pipelines with the same classifier but different pre-processing steps.
The text was updated successfully, but these errors were encountered:
* Add methods get_process_pipelines and get_labels_pipeline to paradigms
* Compute digest from full pipeline Closes#429
* Update docstrings
* Update whats_new.rst
* Add process_pipeline parameter to Results.not_yet_computed
* Add process_pipeline parameter to Results.to_dataframe()
* Update benchmark test
* Fix prepare_process not called when make_process_pipelines called aoutside of get_data
* Complete TODOs
* Add shortcut for make_process_pipelines in utils
* [pre-commit.ci] auto fixes from pre-commit.com hooks
* Remove TODO as discussed (only keep pipeline for first band)
---------
Co-authored-by: Bru <[email protected]>
Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com>
With PR #408 and commit 8c88349, the data processing steps (filtering, resampling, epoching...) are done by a sklearn pipeline.
So we could use the full pipeline (procesing+classification) to create the code that identifies the pipeline in the results, instead of only the classifier.
This would allow to differentiate pipelines with the same classifier but different pre-processing steps.
The text was updated successfully, but these errors were encountered: