Share New Research 
Hi,
1. I'm running a backtest with debug events every minute on a couple of years,
in the end i can't see the whole log in the log tab. how can i get it?
2. If there is an error, i have a link to the a log file but i don't see debug events for the whole period,
i have gaps, for example - backtest on years 2013-2014 on 10 symbols:
"MSFT", "AMZN", "CCE", "GE", "DIS", "MS", "FDX", "YHOO", "CNP", "VZ"
and i have debug at the start of "OnData" event, i get logs for the 1.1.2013, 2.1.2013 and then jump to the end of the year.
Jared Broad
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.
Christopher mathew
Hi Jared, I realise this is 5 years old now, but....
Â
What are the "smarter logging techniques" that you recommend?
Is there a way to delete logs from earlier backtests?
Â
Thanks.
Shile Wen
Hi Christopher,
I suggest logging only important events, meaning focusing on the change events rather logging every time loop. In addition, try Charting when dealing with numerical data that makes sense to be plotted. Furthermore, we increase logging limits based on the users' tier. Using the Debugger might be another way to reduce the need for Logging.
Deleting old backtests won't free logging quota because it's not about disk space, rather it's about restricting logging prices to prevent data theft.
Best,
Shile Wen
Karthik Kailash
Shile Wen if we accidentally use up our log quota (e.g. by running a long backtest without commenting out some Debug statements used for debugging with a shorter backtest), is there any recourse? Or do we just have to wait 24 hours until the quota resets?
Jared Broad
Sorry, not at this time =( I can see why you'd want that though. We can add resetting logs as a Friday project for one of the team.Â
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.
Non Compete
I dont see any logs when a backtest has an error. The console is all rate-limiting messages so the logs I am looking for arne't there. Where is the link to get the logs from a cloud backtest before an error?
Â
Nico Xenox
Hey Non Compete,
you can't really access the logs in the cloud if there was an error in your code, try to debug what you're trying to log so that it prints into the console automatically even if there's an error.
In this case you could also debug your code and add some break points to check if there's any information or you could add if statements to check if there's any values available.
Hope it helps ;)
Eran Maymony
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.
To unlock posting to the community forums please complete at least 30% of Boot Camp.
You can continue your Boot Camp training progress from the terminal. We hope to see you in the community soon!