Closed Equity Tab: Unable to reset Chart after 'Change Scale'
Author: murty
Creation Date: 6/5/2013 3:38 PM
profile picture

murty

#1
I appreciate that there is an option to Change Scale upon right clicking on Closed Equity chart picture on the Closed Equity tab in backtest results window (backtest run on a watch list).

I notice that when I click on 'Change Scale', I get a crash/error window. How can reset scale and get my original Closed Equity chart?

Thanks in advance
profile picture

Eugene

#2
You have to execute the backtest on a DataSet again. If it doesn't work, reopen the Strategy window and rerun the backtest.

On a related note, what does the exception dialog (not a crash) is telling you? Could you Ctrl-C the detailed error report and then Ctrl-V it here? Thanks.
profile picture

murty

#3
It does not fix when I retry backtest. However, it does when I close, reopen and rerun backtest. Attached error msg and screen shot. Please delete the following message and attachment after you review it. Thanks

See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.OverflowException: Value was either too large or too small for a Decimal.
at System.Decimal..ctor(Double value)
at System.Windows.Forms.DataVisualization.Charting.Axis.RoundedValues(Double inter, Boolean shouldStartFromZero, Boolean autoMax, Boolean autoMin, Double& min, Double& max)
at System.Windows.Forms.DataVisualization.Charting.Axis.EstimateLogarithmicAxis(Double& minimumValue, Double& maximumValue, Double crossingValue, Boolean autoMaximum, Boolean autoMinimum)
at System.Windows.Forms.DataVisualization.Charting.Axis.EstimateAxis(Double& minimumValue, Double& maximumValue, Boolean autoMaximum, Boolean autoMinimum)
at System.Windows.Forms.DataVisualization.Charting.Axis.EstimateAxis()
at System.Windows.Forms.DataVisualization.Charting.ChartArea.SetDefaultAxesValues()
at System.Windows.Forms.DataVisualization.Charting.ChartArea.SetData(Boolean initializeAxes, Boolean checkIndexedAligned)
at System.Windows.Forms.DataVisualization.Charting.ChartArea.ReCalcInternal()
at System.Windows.Forms.DataVisualization.Charting.ChartPicture.Paint(Graphics graph, Boolean paintTopLevelElementOnly)
at System.Windows.Forms.DataVisualization.Charting.Chart.OnPaint(PaintEventArgs e)
at System.Windows.Forms.Control.PaintWithErrorHandling(PaintEventArgs e, Int16 layer)
at System.Windows.Forms.Control.WmPaint(Message& m)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
profile picture

Eugene

#4
Thanks for the report. I have never seen this before. It takes an effort to overflow a decimal which ranges from +79,228,162,514,264,337,593,543,950,335 to -79,228,162,514,264,337,593,543,950,335.

The key here is your backtest. I bet it's not done on Fidelity data, and/or it uses huge starting capital? Include a couple of screenshots of the Closed Equity tab - before and after Change Scale. tia.

QUOTE:
Please delete the following message and attachment after you review it. Thanks

Please don't ask.

We're not deleting error reports after reviewing, unless they contain private data (which is by no means the case here). In fact, we've even had to disallow editing own posts by users after a short time (like it's been on the wl4 website). One of the reasons was that some users got into habit of wiping out their questions after getting answered, making technicians look like morons talking to themselves, and inconsiderately depreciating the conversation for other users looking for solutions to related problems.
profile picture

murty

#5
Its done on S&P 500, 30 min data from Fidelity! After upgrading to latest WL (it prompted me to), WL no longer opens up for me (TypeInitializationException), even when I do a fresh install. So, I cant give you any more screenshots. I will try back after a while when there is another upgrade to WL, may be, that will fix the problem.

profile picture

Eugene

#6
OK, looking forward to seeing it after fixing your startup crash (ticket 23490).