Quantopian's community platform is shutting down. Please read this post for more information and download your code.
Back to Community
research notebook error - "WARNING: Loader: No benchmark data found for date range..."

I did not get this warning earlier today. Why am I getting it now?

6 responses

Hey Grant,
Two years of minutely pricing for 1800 stocks is a pretty beefy request you are making. I was just trying to do it myself, to see if I got the same error, and managed to bring down the server.....

We have some work to do (clearly) to make sure that doesn't happen, but for the time being, is it possible to use daily data or try a smaller set of securities?

KR

Disclaimer

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.

Hello Karen,

The code I attached should only be looking at one security at a time:

m = {}  
for s in stocks:  
    try:  
        data = get_pricing(s,start_date='2013-03-20',end_date='2015-03-20',fields='price',frequency='minute')  
        m[s] = data.mean()  
    except:  
        pass  

Should be no problem, right? If figure that get_pricing reads from disk, puts the result in 'data' and then does it all over again for the next security, using the same memory space for 'data' but maybe not? Or there is a memory leak?

Grant

I don't have the research platform access yet, but... is it trying to load all the data into memory?? Is it not all implemented as a Blaze interface to some columnar database like KDB or whatnot?

The truth is we don't know why it took the system down yesterday. We'll be testing it, in staging, next week to try and understand what happened.

What do you mean by "took the system down," the whole research platform? Or just your instance?

The entire server that my instance of research was running on.