price-predictor 1.0.6

Last updated:

0 purchases

price-predictor 1.0.6 Image
price-predictor 1.0.6 Images
Add to Cart

Description:

pricepredictor 1.0.6

Quickly predict the future prices of financial instruments with a
customizable LSTM Recurrent Neural Network
Price-Predictor

You need only a valid yahoo finance symbol like:
“EURUSD=X”,
“^DJI” or
“AMZN”
Download temporarily the financial data from the optionally specified
date (if not specified it starts from july 2010)
A LSTM RNN will be trained and it will automatically predict the
next opening price of the instrument


Installation
With Python and Pip installed, do:
pip3 install price-predictor
Wait for the dependencies to be installed, tensorflow may need a few
minutes.


Command-line usage
Write the following command from your shell:
price_predictor [symbol] [--date (str)] [--target (str)] [--stamps (int)] [--ratio (float)] [--layers (int)] [--epochs (int)]

The symbol is just a short code of the financial instrument that must be available on yahoo finance

The following parameters are optional:

The date must be provided in the ISO format, for example: 2015-01-25
The target can be eiter ‘Open’, ‘Close’, ‘Adj Close’, ‘High’, ‘Low’ or ‘Volume’, the latter only if available, the default target is ‘Open’
The stamps is an integer that identifies the time window of the training subsequences, the default value is 30 which can be seen as roughly a month (it trains to predict tomorrow’s value considering the last 30 days)
The ratio is the percentage used to divide training and test set, the higher the closest to the current trends the prediction will turn out, but it may overfit (just ignore if not know how to use), the default value is 0.90
The layers are the number of layers of the LSTM, the minimum number possible will be always 2, the dafault is 4
The epochs are the number of of epochs the neural network will train, the default is 10 but it can be raised

NB: The argument can be signaled also with a single dash and its first letter (es: -d), no signal is required for the symbol. Also if default values are okay it is possible to entirely omit signaling them. It’s also important to consider that having a close date to today with fewer days than the input stamps may cause unexpected errors.
Usage example:
price_predictor EURUSD=X -d 2021-09-01 -t 'Close' -s 60 -r 0.9 -l 4 -e 50
Meaning: Return tomorrow’s EUR/USD closing price after training on data from the 1st of September 2021, with the first 90% of those data dedicated to the training with a time window perspective of the past two months to predict a new price, the LSTM RNN will have 4 layers and the epochs of training will be 50.
Finally it will also give you a plot of the training and test data prices and the resulting predictions on the test data to visually understand the accuracy of the model.


Documentation
Importing the library
from price_predictor import price_predictor as pp
Then you can use the same function (quick_tomorrow)as in the command line and a few more
tools
You can use 2 functions to query and temporarily store the csv and another
one which is used for the command line to get quick results:
pp.yahoo_finance_csv(code, start_from_date = '2010-07-01', end_to_date = today(), interval = 'd')

pp.quick_tomorrow(code, plot = True, start_from_date, target_value, time_stamps, training_to_test_ratio, n_layers, n_epochs)

end_to_date is the date where there must stop the download of data
interval can be ‘d’ for day, ‘wk’ for weeks and ‘mo’ for months

Then there are two classes you can work with, the basic one is:
model = pp.Price_Predictor(code, start_from_date = '2010-07-01', end_to_date = today(), interval = 'd', time_stamps = 30,
target_value = 'Open', training_to_test_ratio = 0.7, n_layers = 4, n_epochs = 15, verbose = 0,
load_model = False, path_load = 'model_saved', fit_at_start = False, days_forward = 1)

verbose is 0 if you do not want any training info output, 1 if you want the progress bar, 2 if you want the description of each training epoch
load model will load the model stored in the cwd with name = path_load
fit_at_start is used to avoid manually transforming the data and fitting the model with the method .fit_and_test()
days_forward is used only if fit_at_start is True, it indicates the how far is the day you want to predict from the last time stamp

This class has a few methods as in the following usage example:
from price_predictor import price_predictor as pp
import matplotlib.pyplot as plt

fig, axs = plt.subplots(1, 2, figsize=(18,5))

model = pp.Price_Predictor('BTC-EUR', training_to_test_ratio=0.85)
model.plot_data(ax = axs[0])
model.fit_and_test(days_forward = 2)
model.plot_results(ax = axs[1])
plt.legend()
plt.show()
Output:


.plot_data() will plot a chart of the training and test data prices with the point of split
.fit_and_test(days_forward = 2) will scale the data, train the model and test it on the test data, as specified by the parameter it will predict the next price for the day after tomorrow
.plot_results() will plot a chart of the results of the prediction on the test data

model.predict(input_sequence = None, return_info = True)
Output:

WARNING: No input sequence provided, the records of the data downloaded will be used instead.
WARNING: The input sequence on which to forecast is longer than 30 which is the input time stamp and the length of array needed in order to get a prediction,the last 30 records will be considered instead.
In 2 day(s) the price will be: 21021.205
21021.205


return_info = True it will return the warnings and the final print, if False will only return 21021.205
input_sequence = None it will use the data downloaded, instead if an array or list is specified at least as long as the time_stamps specified within the model, the prediction will be based upon the last possible price sequence with exact length of “time_stamps”

Besideds the original parameters it is also possible to access the following relevant attributes of the class in the subsequent way:

the dataframe used
the Min Max scaler used
the training to test split value of the dataframe

model.df
model.scale
model.split_val
It is possible to access the data and the parameters of class also with the following methods:
model.__get_data_frame__()
model.__get_training_set__()
model.__get_test_set__()
model.__get_params__()
It is possible to save and load the trained model as it follows:
model.save_model(dir = 'model_saved')
model_2 = pp.Price_Predictor('BTC-EUR',
load_model = True, path_load = 'model_saved',
fit_at_start = True, days_forward = 2)
As of now the .save_model() method won’t store neither the csv nor the scaled data, as such it is necessary to download them again and then scale them either with fit_at_start = True or with the .fit_and_test() method. In both cases the days_forward parameter must be the same as before.
BETA: The other class is Predict_Iterator, it inherits all the methods and attributes of the Price_Predictor parent class.
Predict_Iterator(code, start_from_date = '2010-07-01', end_to_date = today(),
effort = 0.5, time_stamps = 30)
The parameter effort is used to manage the computational time, it is best left untouched, it’s a coefficient used to concurrently increase or reduce the parameters:

training_to_test_ratio: from 0.70 to 0.90
n_layers: from 2 to 4 with a stronger preference towards 2 layers: max(2, 4*effort)
n_epochs: 2 if effort less than 0.6, 4 if less than 0.75, 10 if less than 0.85 and 15 if greater

The way this class is applied is mainly with the method .get_predictions(), it works like this:
iterate_model = Predict_Iterator('FTSEMIB.MI')
list_of_predictions = iterate_model.get_predictions(days_to_predict = 4)
It will predict the next 4 days’ prices, the parameter days_to_predict will determin the number of training to perform in a loop with different days_forwards (from 1 to days_to_predict).
The trained models will be accessible through the list attribute stored_models as it follows
iterate_model.stored_models
model_1 = iterate_model.stored_models[0]
Each element of the list is a model trained with different future day tergets, once it is accessed it is possible to plot results and manage them as normal Price_Predictor objects.


Notes
It is better to use this tool with financial instruments without a history of substantial price changes, indeed if the price was too high or too low in the past compared to the latest records, the model learnt may be biased towards different levels of prices, it may follow the trend but the amplitude may be completely wrong.
A possible solution to this problem is changing the starting date from which to gather data, so that the model may not be biased towards past averaage prices, or to increase the training to test split ratio (use with care!).


Disclaimer
I am in no way affiliated with, authorized, maintained or endorsed by
Yahoo Finance or any of its affiliates or subsidiaries. This is an
independent and unofficial project.
It is licensed under an MIT license. Refer to the LICENSE file for
more information.

License:

For personal and professional use. You cannot resell or redistribute these repositories in their original state.

Customer Reviews

There are no reviews.