Is there a way to control/filter log message type (debug, info, warn, error) in a backtest?
If not, what is the purpose of having different type of log messages?
thanks
Is there a way to control/filter log message type (debug, info, warn, error) in a backtest?
If not, what is the purpose of having different type of log messages?
thanks
Hi Quantopian, could you give me a feedback on this question?
Maybe I wasn't clear enough. In my algorithms I use the different log type (debug, info, warn, error) to report different type of information but I don't want to have all those messages all the time in the backtest logs. For example I want to enable debug messages only when I see a bug and I like to dig in to details, but usually I am interested only in warning and error messages.
Is that possible to select which messages to display via code or via user interface?
Thank you
Hi Luca,
We haven't developed a log filtering feature. It's certainly something that would be useful, but we haven't gotten to it. One of the reasons that it hasn't happened was the debugger - that debugger is more powerful than logs or log filtering. We invested more time and love in the debugger than in logging.
Has the debugger worked for you?
Dan
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 Quantopian. In addition, the material offers no opinion with respect to the suitability of any security or specific investment. No information contained herein should be regarded as a suggestion to engage in or refrain from any investment-related course of action as none of Quantopian nor any of its affiliates is undertaking to provide investment advice, act as an adviser to any plan or entity subject to the Employee Retirement Income Security Act of 1974, as amended, individual retirement account or individual retirement annuity, or give advice in a fiduciary capacity with respect to the materials presented herein. If you are an individual retirement or other investor, contact your financial advisor or other fiduciary unrelated to Quantopian about whether any given investment idea, strategy, product or service described herein may be appropriate for your circumstances. All investments involve risk, including loss of principal. Quantopian 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.
Thank you for the reply Dan. The debugger works great for code/logic problems, but I like to have my algo collecting information on trends and statistical data, so that I can see those information when I am investigating some particular scenario. It would be nice to have that information logged and available all the time but displayed only when needed.
Thanks.