You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "yuhao yang (JIRA)" <ji...@apache.org> on 2016/12/05 22:06:59 UTC
[jira] [Updated] (SPARK-18724) Add TuningSummary for
TrainValidationSplit
[ https://issues.apache.org/jira/browse/SPARK-18724?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
yuhao yang updated SPARK-18724:
-------------------------------
Description:
Currently TrainValidationSplitModel only provides tuning metrics in the format of Array[Double], which makes it harder for tying the metrics back to the paramMap generating them and affects the usefulness for the tuning framework.
Add a Tuning Summary to provide better presentation for the tuning metrics, for now the idea is to use a DataFrame listing all the params and corresponding metrics.
The Tuning Summary Class can be further extended for CrossValidator.
Refer to https://issues.apache.org/jira/browse/SPARK-18704 for more related discussion
was:
Currently TrainValidationSplitModel only provides tuning metrics in the format of Array[Double], which makes it harder for tying the metrics back to the paramMap generating them and affects the usefulness for the tuning framework.
Add a Tuning Summary to provide better presentation for the tuning metrics, for now the idea is to use a DataFrame listing all the params and corresponding metrics.
The Tuning Summary Class can be further extended for CrossValidator.
> Add TuningSummary for TrainValidationSplit
> ------------------------------------------
>
> Key: SPARK-18724
> URL: https://issues.apache.org/jira/browse/SPARK-18724
> Project: Spark
> Issue Type: Improvement
> Components: ML
> Reporter: yuhao yang
> Priority: Minor
>
> Currently TrainValidationSplitModel only provides tuning metrics in the format of Array[Double], which makes it harder for tying the metrics back to the paramMap generating them and affects the usefulness for the tuning framework.
> Add a Tuning Summary to provide better presentation for the tuning metrics, for now the idea is to use a DataFrame listing all the params and corresponding metrics.
> The Tuning Summary Class can be further extended for CrossValidator.
> Refer to https://issues.apache.org/jira/browse/SPARK-18704 for more related discussion
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org