Skip to content
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

Iteration with Single-Step Progression to Improve Flexibility and Adaptability in Algorithmic Strategies #1111

Open
wants to merge 5 commits into
base: master
Choose a base branch
from

Conversation

IperGiove
Copy link

It is possible to split the run() function into two distinct functions, allowing for a single-step iteration on the ticks:

  • initialize(): Saves the data and the strategy into a self variable.
  • next(): Moves to the next tick in the iteration.

In which scenario do you want to use a next() function instead of a run()?
Using a next() function allows passing any kwargs to the Strategy.next() function. This flexibility enables processing additional information outside the strategy class and injecting it as needed.
However the run function is preserved in order to have the back-compatibility.

For example, one can utilize backtesting.py as an engine to train a reinforcement learning model, requiring an observation and an action at each step.

I've included a test/_iteration.py with a custom TestStrategy that works with both run and iteration, demonstrating how you can inject any parameters into the next function.
Here an example how I use the single step iteration in order to training an Env with gym and stable-baseline3 library:
https://gist.github.com/IperGiove/325832e30df44639ec78a618b84daf3c

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant