MessageBox:
QUOTE:
Error in Visualizer: TabPage: {Performance}, removing.
Object reference not set to an instance of an object.
[OK]
This occurs upon pressing the Cancel button after launch of a backtest. Clicking ok on the Messagebox results in a repeat of the Messagebox, once for each active Visualizer.
Size:
Color:
Oh, then this is intended behavior?
Size:
Color:
I was able to reproduce this under debugger and here's what happens. The SystemPerformance object comes out incomplete and as the loaded performance visualizers do not expect that, they error out and get unloaded by WL.
Is this a problem?
Size:
Color:
No, not a problem. I like clicking through seven MessageBoxes when my strategy gets auto-launched because I touched a PosSizer attribute. :-) It keeps my day from going too fast and keeps my heart rate and blood pressure up.
Size:
Color:
Len, you crack me up! :)
Vince
Size:
Color:
Agreed that graceful error handling is such a nuisance compared to having to close just a single dialog box stating that "Wealth-Lab has crashed, press OK to exit". ;-)
On a serious note, I'm not sure why it's necessary to continue with processing the performance visualizers when the strategy has been canceled. I'll try to ask the developers.
On second thought, this happens when you're quick enough to Escape strategy processing during the data collection phase - which typically doesn't take much time if DataSet is kept up to date.
Size:
Color:
QUOTE:
typically doesn't take much time if DataSet is kept up to date.
Not that short. In my case, about ten seconds for six years of up-to-date S&P 500, on a strategy that builds 34 DataSeries. Well over even this old man's reaction time.
Size:
Color:
For 6 yrs of up-to-date S&P 500, the collection phase takes about 3-4 seconds on my soon 4-year old SSD.
Size:
Color:
34 DataSeries in a strategy? Wow. That's a lot of DataSeries.
Size:
Color:
Hi,
i get the same error message. The only difference is TabPage {Equit Curve} instead of Performance.
first pic
If i am testing from 1999 - 2017 i get this result.
second pic
If i am testing from 2011-14 - 2017 i get this result.
first pic
If i am testing from 2015 - 2017 i get this result.
third pic
does someone know why?
greetings damir
Size:
Color:
Hi Damir,
You get this error for a reason different than topic starter's. It's about the data and you can find it in this FAQ | Position Sizing, Extensions, Miscellaneous > Visualizers >
Oddities on the "By Period" tab
Size:
Color:
Hi Eugene,
thanks.
greetings damir
Size:
Color:
Damir, I'm glad I could help.
Note to future posters: This topic is not a general "visualizer error" thread. Question has been resolved and so it's is closed for new replies. Please look for threads more closely matching your visualizer error(s).
Size:
Color: