Some charts for regression solutions throw an exception if the target variable contains missing values

[gkronber]

This could be the case e.g. when only a part of the whole data set is used for training/testing

NaN is not handled correctly by:

• Scatter Plot
• Error Characteristics Curve
• Residual Histogram

Inf. is not handled correctly by:

• Scatter Plot
• Error Characteristics Curve
• Residual Histogram
• Line chart
• Residuals line chart

[gkronber]

Test script:

using System;
using System.Linq;
using System.Collections.Generic;                            
using System.Collections;

using HeuristicLab.Core;
using HeuristicLab.Common;
using HeuristicLab.Problems.DataAnalysis;
using HeuristicLab.Algorithms.DataAnalysis;

public class MyScript : HeuristicLab.Scripting.CSharpScriptBase {
  public override void Main() {
    var rand = new Random(1234);
    var xs = Enumerable.Range(1, 100).Select(xi=> (double)xi).ToList();
    var ys = xs.Select(_ => rand.NextDouble()).ToList();
    ys[5] = double.NaN;          
    
    var ds = new Dataset(new string[] {"x", "y"}, new IList[] {xs, ys} );
    vars["ds"] = ds;
    var probData = new RegressionProblemData(ds, new string[] {"x"}, "y");
    probData.TrainingPartition.Start = 10;
    probData.TestPartition.End = 90;
    
    double rmsError, cvRmsError;
    var sol = LinearRegression.CreateLinearRegressionSolution(probData, out rmsError, out cvRmsError);
    vars["sol"] = sol;
    
  }
}

[gkronber]

This has been fixed for the line chart. However, the problem still remains for the scatter plot and the error characteristics curve.

For the line chart an exception is thrown if the dataset contains +inf. or -inf.

[gkronber]

fholzing, could you please fix this in the above mentioned views?

[fholzing]

r15785: Added additional filtering logic for double.NaN and double.Inf

[fholzing]

r15787: Made the filtering a little bit more robust

[gkronber]

I tested with the script above and found that the line chart and the residuals line chart works now.

However, the solution is incomplete as the other charts mentioned in the ticket description still produce exceptions. Steps to reproduce:

• Open HL -> New C# Script -> Enter code above, compile and run.
• Open the solution produced by the script
• case (1) Select 'Scatter plot' -> an exception occurs -> expected behavior a scatter plot is shown without the points which are NaN or infinity.
• case (2) Select 'Error Characteristics curve' and select 'All samples' in the 'Samples' drop-down. -> an exception occurs -> expected behavior an ERC is shown whereby the data points which are NaN or infinity are not considered in the calculation
• case (3) Select 'Residual Histogram' -> an exception occurs -> expected behavior: as above

Notes from review of r15785 and r15787:

Line 175 in RegressionSolutionLineChartViewBase.cs

double targetValuesRange = targetValues.Where(v => !double.IsInfinity(v)).Max() - targetValues.Where(v => !double.IsNaN(v) && !double.IsNegativeInfinity(v)).Min();

should also test against NaN in when calculating Max(). The code seems to rely on the fact that comparison of any double with double.NaN is always false. It seems especially smart to skip the NaN comparison but I guess it introduces bugs. So, I strongly recommend to explicitly compare to NaN to make the code more obvious.

(A comment: I wonder if it would work if we remove the NaN comparison when calculating Min()? Another question is whether targetValues.Where(v => !double.IsInfinity(v)).Max() produces the same output for {double.NaN, 1.0, 2.0} and {1.0, double.NaN, 2.0}).

[fholzing]

r15798: Added additional filter for Error Characteristics Curve

[fholzing]

r15790: Added additional NaN-check and also check for both Infinities (+,-) for RegressionSolutionLineChartViewBase

[fholzing]

I added a simple project which performs basic mathematical operations on Inf and Nan, you should find your questions answered.

Basically: Every Operation (+,-,*,/) of any number (including both Inf) with NaN results in NaN The order is the following: NaN, Inf-, <numbers in their natural order>, Inf+ So .Min will result in NaN and .Max in Inf+ (if they occur), otherwise the next/previous element in the order will be taken.

[fholzing]

I can't reproduce case (1) and case(3), case (2) should be fixed. I followed your instruction, but wasn't able to provoke an exception (also played around with the script, like changing NaN to both kinds of Infinity). Please check if you have the latest version.

[gkronber]

Sorry, this was indeed my fault. My working copy was still switched to a branch. I tested the charts and have not found an error.

[gkronber]

Florian, if you are ready please assign it back to me for the final review and we can move it to ready-to-release.

[fholzing]

Additional note from mkommend: Currently the LineCharts just "Hide" Nan/Infs, therefore no gap is visible -> this should be changed.

[fholzing]

r15793: LineCharts will now show a gap instead of hiding NaN/Inf

[gkronber]

r15810: made some changes while reviewing.

Beware list.Remove(elem) removes only the first occurrence of elem.

[gkronber]

r15811: merged r15785,r15787,r15789,r15790,r15793,r15810 from trunk to stable.

fholzing, thanks for fixing this!