[
https://issues.apache.org/jira/browse/MADLIB-1349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nandish Jayaram updated MADLIB-1349:
------------------------------------
Description:
We plan to support only one metric in 1.16 (
https://github.com/apache/madlib/pull/393 ) and that can be one of the
supported metrics and not just accuracy. We should store the name of the metric
that was computed (if computed) in the summary table.
There also seems to be a bug in reporting the {{model_size}} in the summary
table, as it reports a drastically small number compared to the actual model
learnt. Since that is also an update to summary table, it may be a good idea to
fix it as part of this JIRA.
was:
We plan to support only one metric in 1.16
([https://github.com/apache/madlib/pull/393),] and that can be one of the
supported metrics and not just accuracy. We should store the name of the metric
that was computed (if computed) in the summary table.
There also seems to be a bug in reporting the \{{model_size}} in the summary
table, as it reports a drastically small number compared to the actual model
learnt. Since that is also an update to summary table, it may be a good idea to
fix it as part of this JIRA.
> DL: Add metric_type and fix model_size in model summary table
> -------------------------------------------------------------
>
> Key: MADLIB-1349
> URL: https://issues.apache.org/jira/browse/MADLIB-1349
> Project: Apache MADlib
> Issue Type: New Feature
> Components: Deep Learning
> Reporter: Nandish Jayaram
> Priority: Major
> Fix For: v1.16
>
>
> We plan to support only one metric in 1.16 (
> https://github.com/apache/madlib/pull/393 ) and that can be one of the
> supported metrics and not just accuracy. We should store the name of the
> metric that was computed (if computed) in the summary table.
> There also seems to be a bug in reporting the {{model_size}} in the summary
> table, as it reports a drastically small number compared to the actual model
> learnt. Since that is also an update to summary table, it may be a good idea
> to fix it as part of this JIRA.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
