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.
Change List
workflow description figures
Update sanity checker shortcut with protectTextSharedHash param (build failed #234)
Some more licenses (Make tests a little less flaky #221)
wrapped spark model classed using reflection (part 1 of 2) (Fix indices in LOCO for record-level insights and add more robust tests #216)
wrapped spark estimators so that they return op wrapped models with prediction return type (part 2a of 2) (Release 0.5.1 #222)
wrapped spark estimators for new models added (part 2b of 2) (Random param builder for random hyperparameter search in model selectors #238)
Moved code out of spark ml workspace and added comments - no code changes after tickets (TransmogrifAI on Apache Zeppelin #239)
use prediction rather than raw prediction
Fix package access level on OpEstimatorBaseSpec (Error in
transmogrifai gen
when field has an underscore #205)internal OP test base class
fix the issue that certain text strings can be entirely removed by our tokenizers, but null tracking step for text map vectorizers just checks for the presence of a key
fix dead lock in OpCrossValidation.findBestModel happened due to the fact that when running splits processing in parallel these threads would try to access spake stage params on the same stages.
Migration Guide
OpLogisticRegression() is in progress (evaluator needs updates)
may use BinaryClassificationModelSelector() instead
need to add .setProbabilityCol($probCol) to evaluator in workflow definition to make sure that the evaluator will get the correct probability column to do the calculation