-
Notifications
You must be signed in to change notification settings - Fork 29
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Generating technical indicators for intervals and periods #7
Comments
Hi, Best, |
Thanks for clarifying Mohammed, Is it correct to assume that the only lines that need to be updated to change between the different different intervals and prediction timeframes are the following:
Changes to the following for Feature selection for Interval 3 at the 7 day prediction:
and swapping:
for:
I'm first looking to reproducing your 7 day price forecast using the different models (hence the interval3/seven combination), but if it's easier to supply a copy of your notebook used to generate the Thanks again for all your help. |
Hi, Edit: |
I want to offer a new point of view, and my colaboraty Why this stock prediction project ? Testing with +-30 models. Multiple combinations features and multiple selections of models (TensorFlow , XGBoost and Sklearn ) |
Hi,
After creating the the master BTC_Data.csv file, it needs to be broken down into the respective indicator files for the different intervals (1, 2, 3) and periods (1, 7, 30, 90 days etc). There seems to be a loose framework for the interval interval file generation in the
Feature_Selection
notebooks, but I just want to confirm the methodology before proceeding.Do you already have this code in a loop that will generate each file automatically, or do the notebooks require manually editing for each iteration? If the latter, can you please clarify which lines need to be updated in
Feature_Collection_reg.ipynb
andFeature_Collection_cls.ipynb
to generate all the different combinations of technical indicators on each run?Thanks,
J.
The text was updated successfully, but these errors were encountered: