Quantopian's community platform is shutting down. Please read this post for more information and download your code.
Back to Community
Using Global Domain Calendars on Self-Serve Data
Raphael Coelho
edited Jul 17, 2019
Seeking Help Research Global Equity Self Serve Data

Hello,

I've uploaded a dataset with daily Brazilian inflation rate and I'm trying to run it through a pipeline with BR_EQUITIES trading calendar. I couldn't set the dataset calendar to comply with Brazilian one.

Does anyone has an idea about how to do so?

start_date = '2017-04-01'  
end_date = '2018-01-01'

calendar = BR_EQUITIES.calendar

# Roll input dates to the next trading session.  
start_date = calendar.minute_to_session_label(pd.Timestamp(start_date, tz='UTC'))  
end_date = calendar.minute_to_session_label(pd.Timestamp(end_date, tz='UTC'))


from quantopian.pipeline import Pipeline  
from quantopian.research import run_pipeline  
from quantopian.pipeline.data.user_58af26be81aa9409a19d02db import daily_ipca_rate

daily_ipca_rate.signal.calendar = BR_EQUITIES.calendar

pipe = Pipeline(  
    columns={  
        'my_dataset': daily_ipca_rate.signal.latest  
    },  
    screen=daily_ipca_rate.signal.latest.notnull(),  
    domain=BR_EQUITIES,  
)
df = run_pipeline(pipe, start_date, end_date)  
df.head()  
ValueErrorTraceback (most recent call last)  
<ipython-input-21-e40302541cff> in <module>()  
     22     domain=BR_EQUITIES,  
     23 )  
---> 24 df = run_pipeline(pipe, start_date, end_date)  
     25 df.head()

/build/src/qexec_repo/qexec/research/api.py in run_pipeline(pipeline, start_date, end_date, show_progress, chunksize)
    490             show_progress=show_progress,  
    491             pipeline_engine=pipeline_engine,  
--> 492             holdout_manager=holdout_manager,  
    493         )  
    494     # The docstring is defined at module scope to get correct indentation.

/build/src/qexec_repo/qexec/research/_api.pyc in inner_run_pipeline(pipeline, start_date, end_date, show_progress, chunksize, pipeline_engine, holdout_manager)
    724     """Internal implementation of quantopian.research.run_pipeline.  
    725     """  
--> 726     domain = pipeline_engine.resolve_domain(pipeline)  
    727     adjusted_start_date = domain.roll_forward(start_date)  
    728     adjusted_end_date = domain.roll_forward(end_date)

/build/src/qexec_repo/zipline_repo/zipline/pipeline/engine.pyc in resolve_domain(self, pipeline)
    863         """Resolve a concrete domain for ``pipeline``.  
    864         """  
--> 865         domain = pipeline.domain(default=self._default_domain)  
    866         if domain is GENERIC:  
    867             raise ValueError(

/build/src/qexec_repo/zipline_repo/zipline/pipeline/pipeline.py in domain(self, default)
    269     def domain(self, default):  
    270         """  
--> 271         Get the domain for this pipeline.  
    272  
    273         - If an explicit domain was provided at construction time, use it.

/build/src/qexec_repo/zipline_repo/zipline/pipeline/pipeline.pyc in domain(self, default)
    310                 raise ValueError(  
    311                     "Conflicting domains in Pipeline. Inferred {}, but {} was "  
--> 312                     "passed at construction.".format(inferred, self._domain)  
    313                 )  
    314             return inferred

ValueError: Conflicting domains in Pipeline. Inferred EquityCalendarDomain('US', 'XNYS'), but EquityCalendarDomain('BR', 'BVMF') was passed at construction.
2 responses
Russell Cox
Sep 2, 2020

Did you resolve this one? I am facing the same issue with GB_EQUITIES.

Russell Cox
Sep 2, 2020

I solved my own problem. I am using the Alphalens tutorial 5 quick start template and have converted it to use UK stocks with GB_EQUITIES as the domain. I get the equivalent of the error reported above. However, when I remove the references to sector all is well ie
sector = Sector() 

return Pipeline(  
    columns = {'factor_to_analyze': factor_to_analyze},  
    screen = universe & factor_to_analyze.notnull() & **sector.notnull(),**  
    domain=GB_EQUITIES,  
)
About Quantopian
Careers
Community
Events
Documentation
Academia
Lectures
Status
Facebook
Twitter
LinkedIn
YouTube
Terms of Use
Privacy Policy

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.