In WL8, after I finished some edits I click "Run Backtest".
While this runs I find it a good idea to save my changes, so I click "Save".
WL8 responds with an Exception.
While this runs I find it a good idea to save my changes, so I click "Save".
WL8 responds with an Exception.
Rename
Not an exception since there's nothing in the log viewer and no exception message thrown. I guess you're talking about that innocuous "Object reference not set..." error in the status bar?
Can you send the strategy to us via email? support@wealth-lab.com.
btw, I made a fix for B23 to make the error spell differently. But as this "issue" is easily reproducible I think we may simply disable the Save and Save As buttons during a backtest in progress to avoid it altogether. Dion, what do you think?
Well, it seems to be an exception. Whether it gets displayed in a dialog and/or in the log viewer depends on how the exception is handled in WL8.
The problem is easy to recreate:
Open a strategy.
Change a setting like flipping it from single to multiple positions and back again.
Back test the strategy. While the back test is running, hit the save button.
The back test does not complete. Object reference not set to an instance of an object appears.
No results appear for the back test.
To confirm back test results should have been generated:
Close the strategy and reopen it.
Back test the strategy and let it complete. Do not hit save (if available).
Back test results appear.
The problem is easy to recreate:
Open a strategy.
Change a setting like flipping it from single to multiple positions and back again.
Back test the strategy. While the back test is running, hit the save button.
The back test does not complete. Object reference not set to an instance of an object appears.
No results appear for the back test.
To confirm back test results should have been generated:
Close the strategy and reopen it.
Back test the strategy and let it complete. Do not hit save (if available).
Back test results appear.
Good to know. I've never tried doing that before but for sure won't ever do that now!
QUOTE:
simply disable the Save and Save As buttons during a backtest
I guess this is the perfect solution...
Yes I have the same error many times, till I figure not click Save while running a backtest
Long ago, I adopted a workflow to Save before running a backtest. Why? Because logic mistakes in strategy code can cause fatal errors.
QUOTE:
I guess this is the perfect solution...
Let's do it unless Dion has objections.
Your Response
Post
Edit Post
Login is required