Back to Community
New Datasets, Pipeline UX Improvement, and More

Hey Everyone,

We have a number of platform updates to share:

New Datasets: Geographic Revenue Exposure, Long Term Estimates, and Broker Recommendations.

One of our goals this year is to add a lot more data to Pipeline so that you have more ways to come up with successful strategies that are eligible for the contest (and an allocation). Today, we added 3 new datasets from FactSet’s catalog, and all 3 are usable in the contest. Check them out and see if they spark any new ideas!

To learn more about each dataset and how to use them, see the Data Reference:

We plan on making a follow-up post that covers each dataset in more depth, but in the meantime, the data reference should give you a lot of information on each one!

Pipeline Progress Bars

In Research, running a pipeline with run_pipeline now includes a progress bar to give you a sense of how much of your pipeline has been computed and how much is left. At a high level, it computes the progress by determining the total number of terms that the pipeline needs to compute and the % that have already been computed. This should make it easier to work with pipelines in research, especially those that take longer to run.

Backtest Instance Classes Upgraded

We upgraded the hardware or ‘instance class’ on which backtests are executed so you should start to see backtests running a little faster than they did before. Generally speaking, we see the most extreme speed improvements with software updates, but this hardware upgrade should lead to a slight improvement here. It’s also worth noting that the new instance class has a bit more memory, so if you had a backtest that ran out of memory before, you should try running it again.

Debugger Fix

Previously, the debugger was crashing for algorithms that used certain quantopian module attributes. Most commonly, this occurred in algorithms that used the optimize.experimental module. We pushed a fix so it shouldn’t crash any more.

Thanks to Gary for originally reporting the issue.


For those who celebrate it, happy 4th of July!

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.

3 responses

hey my name is kaiwalya harkare i am from India . I am new to algorithmic side of trading and python data visualization but i have a strong base in fundamental analysis . I am 16 yrs old will you help me smash bugs . I am not very good at this .

Hey Jamie, this functionality is excellent - thank you for the update!

UX must be User Experience