Quantopian's community platform is shutting down. Please read this post for more information and download your code.
Back to Community
Possible Issue with Estimize Data?

I've been playing around with Seong's Post-Earnings Drift Trading Strategy with Estimize (PEAD) algo and looked at incorporating the Wall Street EPS and Revenue numbers (reported by Estimize) as additional data points, but got strange results. I then started to compare the numbers that were being output in the log with what was on the Estimize site and discovered that the vast majority of the time the numbers were incorrect. The Estimize ESP, actual EPS, and even the Estimize revenue and actual revenue numbers all matched up perfectly, but the Wall Street EPS and Wall Stree revenue were wrong more often than not. A little more digging and it appears that the data shown is often from other quarters. Here is a sample log dated 1-24-2014 (I formatted it for easy reading and just made a screenshot of the table):

Screen Shot of Log Output (formatted)

Columns I and J are what's shown in the log and columns K and L are what the numbers should be. I then included notes about where I actually found numbers that correlated to the numbers reported in the log.

I've done a lot of testing and reviewing across many different dates and it's always the same; most of the data is incorrect (although not all). Thinking maybe it was a problem with the free data, I subscribed to the full Estimize data set and it's incorrect even up to the present. I've attached a short backtest of what I ran. I just took Seong's original algo, included the "consensus_wallstreet_eps_free" import and created two additional factors to show the Wall Street EPS and revenue. Everything else is the same.

Any idea what might be going on?

Scott

5 responses

Has anyone had a chance to look into this issue?

Scott

Yikes!

We're digging in here. Will let you know what we find.

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.

any result?

Hi Peter,

We were able to diagnose the problem yesterday. We're working on a solution. It will likely require re-building the data set so it won't be a quick fix but it's top of the queue for us and we're continuing to hack away at it.

Thanks
Josh