Stacking-AddScatter-plots-in-ScottPlot

After a while, I finally figured out the fundamental problem with the AddScatter() call. The X and Y arrays are passed into this call by reference (pointer) as in:

CODE:
plt.AddScatter(ref xVol, ref yPriceChg);
//However, AddScatter does *not* modify these arrays as the "ref" prefix would suggest

although the documentation does not suggest this and this design is somewhat against how C# programs are typically architected. However, because these arrays are passed by reference, these arrays cannot be changed (after calling AddScatter) until the plot is finally rendered; otherwise, that plot will be lost. Although there are several possible workarounds, if one wants to call AddScatter() in an outer For loop, the only realistic option is to use a two-dimensional jagged C# array (which isn't actually jagged in this case) for passing the X and Y arrays into AddScatter. And that's the solution given below.

CODE:
public override void Cleanup(BarHistory bars)
{
   if (ExecutionDataSetName == null) //only plot stats in single-symbol mode
   {
      Plot plt = new ScottPlot.Plot(700,500);
      plt.XAxis.TickLabelNotation(multiplier: true); //use engineering notation
      plt.Title("Price change vs Volume for " + bars.Symbol);
      plt.XLabel("Volume");
      plt.YLabel("Price change");

      List<Position> positions = GetPositions();
      double[][] xVol = new double[positions.Count][], yPriceChg = new double[positions.Count][];
      for (int posIdx = 0; posIdx < positions.Count; posIdx++)
      {
         Color plotColor = plt.GetNextColor();
         Position pos = positions[posIdx];
         xVol[posIdx] = new double[6]; yPriceChg[posIdx] = new double[6]; //plot 6 point per position
         for (int barOut = 0, barIn = pos.EntryBar-2; barOut < yPriceChg[posIdx].Length && barIn < bars.Count; barOut++, barIn++)
         {
            xVol[posIdx][barOut] = bars.Volume[barIn];
            yPriceChg[posIdx][barOut] = bars.Close[barIn] - bars.Close[barIn-1];
            if (barOut == 2)
               plt.AddPoint(xVol[posIdx][2], yPriceChg[posIdx][2], plotColor, 10, MarkerShape.asterisk);
            else if (barOut < 2)
               plt.AddPoint(xVol[posIdx][barOut], yPriceChg[posIdx][barOut], plotColor, 12, MarkerShape.openDiamond);
         }
         plt.AddScatter(xVol[posIdx], yPriceChg[posIdx], plotColor, lineWidth: (pos.ProfitPercent > 3.0) ? 2F:1F,
            lineStyle: (pos.ProfitPercent > 3.0) ? LineStyle.Solid:LineStyle.Dot, label: bars.DateTimes[pos.EntryBar].ToString("MM/dd/yy"));
      }
      plt.Legend();
      plt.SaveFig(System.IO.Path.Combine(Environment.GetFolderPath(Environment.SpecialFolder.Desktop), @"priceChgVsVolume.png"));
   }
}

The resulting plot below plots six PriceChange-vs-Volume points as groups (of different color) for six different positions taken for the ADNT stock. Those bar positions that made money are connected with solid lines; whereas, those bar positions that lost money are connected with dotted lines. The bar points prior to each buy are plotted with diamonds; the bar depicting the day of the buy is plotted with an asterisk; and the bars after the buy are plotted with a small dot. The legend lists the buy date for each of the six positions traded.
Now if someone can spot a behavioral difference from the positions that made money (the solid lines) from those that lost money (the dotted lines), please let me know.