Back to Community
Warnings/Errors not shown on build screen?

Apologies if this is not the correct forum to ask for help with development-

When working in the IDE, it would be useful to be able to see log.warn and log.error output after hitting the build button.


3 responses

@Rob, +1 and great idea. We have been discussing a related idea - what if we ran a very short backtest as part of the ctrl-b/build button action. We were thinking we could run daily pricing through the algorithm. That way you'd get a high level picture of the behavior, and flush out more of the small bugs before doing a full blown test. What do you think?


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.

@fawce yes, that would be very helpful to quickly test the algo against a single tick(the latest tick available?), and not only get debug output but also get a performance estimation for a smaller set of data.

What would be even COOLER would be if the system had instant evaluation and display, similar to the upcoming LightTable IDE: (look at 1:10)

@Rob, calculating performance for the daily run is an awesome idea.

We've been following LightTable too, and drawing inspiration to shorten the time from code to results as much as possible. Clearly we can do more :).

We also like what Jaime Wong did at Khan for programming and loved the video talk from Bret Victor that Jaime references in that blog.

Please keep the ideas coming!