-
Notifications
You must be signed in to change notification settings - Fork 1
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
Add MeanStdScaling transform #17
Conversation
Codecov Report
@@ Coverage Diff @@
## main #17 +/- ##
==========================================
+ Coverage 94.50% 99.09% +4.58%
==========================================
Files 8 9 +1
Lines 91 110 +19
==========================================
+ Hits 86 109 +23
+ Misses 5 1 -4
Continue to review full report at Codecov.
|
I noticed you've been merging branches into this one, can you try rebasing instead in the future? It keeps the git history much more clean. |
I have done some refactoring to always populate the Overall it seems better - much less overloading. One thing is |
Why did you decide to go with dims being consistent with eachslice instead of what we are already doing in FeatureEngineering? |
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.
Overall looking a lot cleaner now I think
Because the other transforms so far use dims consistent with eachslice. But I think this is the first transform where |
The other mutating transforms follow eachslice, but the non mutating follow the mapslices convention. So yeah I think we should move everything to follow the mapslices convention for dims |
Also mutating test for Vector
Remove 3D array test for now
- Re-applying scaling to a different array - AxisArray, KeyedArray, NamedTuple - Other minor additions and improvements
- mean, std are either passed in or computed from data upon construction - general apply methods pass `name` keyword to `_apply` for compatibility - add `kwargs...` to general `apply` for tables and `_apply` in HoD transform, for compatibility - add missing re-apply test for NamedTuple
- mean, std are either passed in or computed from data upon construction - general apply methods pass `name` keyword to `_apply` for compatibility - add `kwargs...` to general `apply` for tables and `_apply` in HoD transform, for compatibility - add missing re-apply test for NamedTuple
Required changing the convention for dims from eachslice to mapslices
missed in rebase
14d4d46
to
f1ad4dc
Compare
Sorry, I made a mess of commits trying to rebase after #19 . I will squash before merging. |
Closes #3
Note: the notion of
dims
is now consistent withmapslices
andStatistics.mean/std
rather thaneachslice
. To do that, I inverted the dims passed to the generalapply!
method for arrays.Statistics.mean/std
was used inFeatureEngineering
. Related issue: #18