[
https://issues.apache.org/jira/browse/SPARK-14033?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15206455#comment-15206455
]
Daniel Siegmann commented on SPARK-14033:
-----------------------------------------
To me, the semantics of this proposal are _less_ clear. An estimator as a thing
which produces a transformer is clearer to me than a self-configuring
transformer. The current design creates a distinction between code which does
the training (the estimator) and the code which does the scoring (the model,
which is a transformer).
I also think there's a big difference between being able to mutate the
hyper-parameters on an estimator and having the fit method modify the model
parameters. If anything, I'd rather see the estimator be completely immutable.
> Merging Estimator, Model, & Transformer
> ---------------------------------------
>
> Key: SPARK-14033
> URL: https://issues.apache.org/jira/browse/SPARK-14033
> Project: Spark
> Issue Type: Improvement
> Components: ML
> Reporter: Joseph K. Bradley
> Assignee: Timothy Hunter
> Attachments: StyleMutabilityMergingEstimatorandModel.pdf
>
>
> This JIRA is for merging the spark.ml concepts of Estimator and Model.
> Goal: Have clearer semantics which match existing libraries (such as
> scikit-learn).
> For details, please see the linked design doc. Comment on this JIRA to give
> feedback on the proposed design. Once the proposal is discussed and this
> work is confirmed as ready to proceed, this JIRA will serve as an umbrella
> for the merge tasks.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
