Does somebody know how much days before the actual release date Estimize has its data ready?
Playing around with it I was just able to see hours(4-5) before the release date.
quantity: 1- self.Time :2019-01-30 16:00:00
Release Date: 2019-01-30 21:00:00
Is this because of Estimize or is my code wrong?
Thanks in advance!
Nico Xenox
I just saw u have to pay for the dataset, so im sorry for posting
Newoptionz
Hi Nico Xenox
Did you pay? Did it work better? I subscribed to the estimize data for a month, but I had no idea how to code it, so would really like to try ideas and I would re-subscribe if I could get stuff to work, lol. Please keep sharing.
Nico Xenox
Hey Newoptionz,
I found a better way for my problem without having to pay for a dataset. I just simply add the symbols to the notebook that I need the future earnings dates and import them via objectstore into the algo. If you're interested I can provide a example ;)
sry for not replying but I had to change everything for it to fit my research.
Newoptionz
Yes Please.
I just re-subscribed to the estimize dataset, still trying to figure out how to use it. Seems to me I have to build a list to track the past earnings and the price affects before and after earnings and see how these correlate to the various estimize prediction differences. All without viewing the real data, lol.
Newoptionz
Nico Xenox
I would say another method would be to track the avg number of days between earnings for a company and then use that as the future estimate of the earnings release. Most companies do not even say when they are going to release earnings.
Traders also watch the overall volatility of the weekly options market for spikes in the volatility, these signal most probable earnings weeks. Maybe there is away to test that in a Jupiter notebook.
Nico Xenox
Hey Newoptionz,
For this method you will first have to select the tickers you want to trade and after that import them into jupyter notebook:
2. Import the tickers from the objectstore into the notebook
3. If you save the same tickers multiple times into the list check the list and delete them
4. Request dates(NOTE: it will take some time)
5. Save the dictionary into ObjectStore and import it into your algo
6. Adjust dates and Symbols (You can not save Quantconnect symbols into the objectstore → Extract symbol values and rename with quantconnect symbol)
7. delete first values of each symbol because that date already happened
8. Last step.. not sure if it is necessary but I import every year a new set of symbols and have to adjust the dates dictionary to delete the already happened values.
Hope it helps ;)
Newoptionz
Thanks, looks complicated, I'll give it a go.
Newoptionz
Nico Xenox Well, I need help. I open up a new test.ipynb and then everything works, but it seems to only get the dates for one symbol and I don't know how to see the dict_list with the dates that are filtered.
Nico Xenox
Hey Newoptionz,
you just have to use objectsotre if ou want to import tickers from the QC algo to the notebook or from other algos. In this case you have the tickers already in a list which means you can just use this:
OXY either doesnt seem to have data or the time interval was set when OXY changed name or doesnt trade anymore. I set up try and execpt because sometimes they dont have values. If you want to know you will have to do a manual history request.
Hope it helps ;)
Newoptionz
Hi, I see I had a typo on the one stock it should be ‘PBF’. When I shut down the Juypter test.ipynb and re-open it, now the cells run, but the print statements don't show any output, there is just ‘…’ (three dots) where the output should be, I had a print(symbols) that worked befor and the print(date) worked aswell.
Nico Xenox
You either have to restart the kernel. I tried it again and added the print statements that you used. It works with mine… (NOTE: I changed qb to self. self = qb)
Newoptionz
Hi Nico Xenox
No, still does not work. Both print(date) work, but when it trys to enter ‘for x in date[x]:’ the code bombs. I think it trys to convert the dataframes date values to a array and then it tries to add that array to a dictionary using the symbol as the key, but it fails. Not sure how you would work with such a dictionary if it worked? That would be a whole other adventure.
The following is not working
Nico Xenox
Hey Newoptionz,
you're right. When executing the code you provided me I get an empty dictionary. But the way I did it it worked. So I tried to find the problem and even tho I found it, I absolutly dont understand why that is so…
You just have to add these three lines to the code(It might be less, didnt test it):
I even checked if the dates of WLL or BLK are the ones you see on the dictionary but that isnt the case. It does work with the ones provided in the tickers list. Here is an image of the result adding these lines to your code:
It seems like that the notebook needs some sort of request to work or something like that I might be wrong tho.
The code(just added the lines above):
It worked for me because every time I started up the notebook I had this block:
Either way, I hope it helps ;)
Newoptionz
Nico Xenox
Thanks, that worked. I am at the following point, which works, but not sure what to do with the data, other to say it is an interesting excercise in data manipulation
Nico Xenox
Hey Newoptionz,
now that you have this data you will be able to do earnings plays for each stock. just save the dictionary into the objectstore and use it in a algorithm. Now the advantage is that you know the date before it will happen, normally you are not able to do that.
Newoptionz
Hi Nico Xenox, yes well that would work for backtesting earnings plays, not really for live trading. I will try give the backtesting a go and post here results etc…
Nico Xenox
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 QuantConnect. In addition, the material offers no opinion with respect to the suitability of any security or specific investment. QuantConnect 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. All investments involve risk, including loss of principal. You should consult with an investment professional before making any investment decisions.
To unlock posting to the community forums please complete at least 30% of Boot Camp.
You can continue your Boot Camp training progress from the terminal. We hope to see you in the community soon!