Skip to content
  • Feynman Liang's avatar
    28a98464
    [SPARK-10097] Adds `shouldMaximize` flag to `ml.evaluation.Evaluator` · 28a98464
    Feynman Liang authored
    Previously, users of evaluator (`CrossValidator` and `TrainValidationSplit`) would only maximize the metric in evaluator, leading to a hacky solution which negated metrics to be minimized and caused erroneous negative values to be reported to the user.
    
    This PR adds a `isLargerBetter` attribute to the `Evaluator` base class, instructing users of `Evaluator` on whether the chosen metric should be maximized or minimized.
    
    CC jkbradley
    
    Author: Feynman Liang <fliang@databricks.com>
    Author: Joseph K. Bradley <joseph@databricks.com>
    
    Closes #8290 from feynmanliang/SPARK-10097.
    28a98464
    [SPARK-10097] Adds `shouldMaximize` flag to `ml.evaluation.Evaluator`
    Feynman Liang authored
    Previously, users of evaluator (`CrossValidator` and `TrainValidationSplit`) would only maximize the metric in evaluator, leading to a hacky solution which negated metrics to be minimized and caused erroneous negative values to be reported to the user.
    
    This PR adds a `isLargerBetter` attribute to the `Evaluator` base class, instructing users of `Evaluator` on whether the chosen metric should be maximized or minimized.
    
    CC jkbradley
    
    Author: Feynman Liang <fliang@databricks.com>
    Author: Joseph K. Bradley <joseph@databricks.com>
    
    Closes #8290 from feynmanliang/SPARK-10097.
Loading