Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

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

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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Open
IperGiove wants to merge5 commits intokernc:master
base:master
Choose a base branch
Loading
fromIperGiove:master

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

aifirstd3v and Vitalii-kripto reacted with thumbs up emoji
@kernc
Copy link
Owner

kernc commentedOct 31, 2025
edited
Loading

Ok, I think I understand the issue. You canpass custom data to the strategy logic (df columns in addition to OHLC), but you can't pass custom objects (your RL optimizer object that tells your next action). In that case, you can:

df['model_obj']=np.repeat(rl_model_obj,len(df))

and innext() use that (i.e.self.data.model_obj[-1]).

Would that work for you?

Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@IperGiove@kernc

[8]ページ先頭

©2009-2025 Movatter.jp