This repository has been archived by the owner on Jul 16, 2021. It is now read-only.
Shuffler Transformer #135
Merged
Shuffler Transformer #135
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds a
Shufflertransformer to thedata/transformsmodule and resolves #127. I've also separated theTransformertrait intoTransformerandInvertible. We require an additional trait import to use theinv_transformbut otherwise things are unchaged. This lets us define transformers which cannot be inverted.The intention is that this transformer can be directly used by users to shuffle their input data before running the model. We could also use this transformer within the cross-validation and other modules.
I think that this module should not be used within the
learningmodule - this is because the transformer consumes the input data.