Back

Killing backtest doesn't seems to work

When I close a backtest, it seems that the process in the background is not being killed and

it continue to pop-back in the UI.

Update Backtest








You need to delete it, not simply close it.

0

Yep, and sometimes you need to refresh your browser or press 'algorithm lab' and select backtest to get your latest backtests run again for heavy time consuming algos on a long time period for instance.

0

Thanks, I have tried the whole day to run a basic covered call strategy it takes ages then crashes, only work for very short time-frames

0

Can you share you algorithm? I am also running an algo for a couple of days now on SP500 (500 stocks). Takes some day to calculate daily. But is works...and it (very) profitable. I will share my algorithm as I want others to have a look before livetrading it and I want some ATR volatility protection in it. What I found out is that I first warm up all my indicators in the initialize(), then I warm up in the securities changed as if I do calculate all my indicators in the ondata functions I get time outs. During my debugging I put try-except parts to find out where it went wrong. My Python is not so good as C#, but I guess adding this:

try:
... x = int(input("Please enter a number: "))
... break
... except ValueError:
... print("Oops! That was no valid number. Try again...")

might help. If you are trading options or futures it might be that the security is not in the portfolio anymore and that will throw and error. I believe Derek Tishler is quite good at debugging algos for errors.

0

Quant Trader "select backtest to get your latest backtests run again" -- behind the scenes heavy algorithms keep running even if backtest closed. They currently send updates every 2-backtest days maximum - so if your algorithm takes 2min per day - it might be 3-4min beween updates. 99% of people backtests only take a few seconds per day so don't notice.

0

The material on this website is provided for informational purposes only and does not constitute an offer to sell, a solicitation to buy, or a recommendation or endorsement for any security or strategy, nor does it constitute an offer to provide investment advisory services by QuantConnect. In addition, the material offers no opinion with respect to the suitability of any security or specific investment. QuantConnect makes no guarantees as to the accuracy or completeness of the views expressed in the website. The views are subject to change, and may have become unreliable for various reasons, including changes in market conditions or economic circumstances. All investments involve risk, including loss of principal. You should consult with an investment professional before making any investment decisions.


Jared Broad , thank you. I have restarted them this morning and after 8 hrs they seem to be hanging again. One stopped again on 25 feb 2008, so still 10 years to go for back testing. I refreshed the Algorithm lab and it took a while. The two back tests are back and again they start in 2000....the first years till 2006 run fast and then they get slower and slower and in 2008 hang. Any ideas? I have had this now twice, so seems reproducable. I have shared my algo and created a support ticket.

0

Ok ty we'll answer as soon as possible. 

0

The material on this website is provided for informational purposes only and does not constitute an offer to sell, a solicitation to buy, or a recommendation or endorsement for any security or strategy, nor does it constitute an offer to provide investment advisory services by QuantConnect. In addition, the material offers no opinion with respect to the suitability of any security or specific investment. QuantConnect makes no guarantees as to the accuracy or completeness of the views expressed in the website. The views are subject to change, and may have become unreliable for various reasons, including changes in market conditions or economic circumstances. All investments involve risk, including loss of principal. You should consult with an investment professional before making any investment decisions.


I have started an algo over 10 hours ago and it is still going, the same simple covered call on bloomberg takes 6 seconds. There is something wrong, maybe the resource management is adding too much overhead. Switching between backtests.

No Algorithm should be allowed to run for that long, It will just hog the resources.

0

Actually it took 16h user time but just over 1h cpu time

2016-01-01 00:00:00 Launching analysis for bee8acdffab0c6b4b0a906aa7d8ed3fd with LEAN Engine v2.4.0.1.3036
2016-01-04 10:01:00 Warning: The QQQ equity security was set the raw price normalization mode to work with options.
2017-12-29 16:00:00 Algorithm Id:(bee8acdffab0c6b4b0a906aa7d8ed3fd) completed in 8029.21 seconds at 0k data points per second. Processing total of 1,039,565 data points.

0

Update Backtest





0

The material on this website is provided for informational purposes only and does not constitute an offer to sell, a solicitation to buy, or a recommendation or endorsement for any security or strategy, nor does it constitute an offer to provide investment advisory services by QuantConnect. In addition, the material offers no opinion with respect to the suitability of any security or specific investment. QuantConnect makes no guarantees as to the accuracy or completeness of the views expressed in the website. The views are subject to change, and may have become unreliable for various reasons, including changes in market conditions or economic circumstances. All investments involve risk, including loss of principal. You should consult with an investment professional before making any investment decisions.


Loading...

This discussion is closed