-
Notifications
You must be signed in to change notification settings - Fork 314
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
[Feature Request] Support for Integrating Custom PettingZoo Environments with TorchRL's PettingZooEnv #2461
Comments
There is an example of adding a new pettingzoo env from scratch here facebookresearch/BenchMARL#84 |
Essentially the process is just:
PettingZooWrapper( MyPettingzooEnv( **config) ) |
@matteobettini thanks for the link. The issue here is that i have a pettingzoo.AECEnv |
Benchmarl is not comaptible with turn-based AECEnvs (facebookresearch/BenchMARL#76) But the torchrl wrapper is |
Okay thanks for the information. Would you have any recommendation for AECEnv then @matteobettini ? Because I cannot make it parallel (the turn-based factor is important there). |
You can put You just can't use benchmarl as of now. You can use torchrl |
Thanks a lot! |
Motivation
I’ve created a custom PettingZoo environment and I’m looking to integrate it with
benchmarl
, which is based ontorchrl
. Currently, thePettingZooEnv
class is implemented intorchrl
, but it's unclear what the process is for adding a new custom PettingZoo environment.This feature request is motivated by the need for easier registration and compatibility of custom environments with
benchmarl
andtorchrl
. It could help streamline the process for users who develop their own PettingZoo environments.Solution
I would like to see a clear and concise method to register new PettingZoo environments, either through documentation or a straightforward integration pathway in
torchrl
. Ideally, this would allow custom PettingZoo environments to be added with minimal effort, leveraging the existingPettingZooEnv
structure intorchrl
.Alternatives
An alternative approach could be to manually modify the
PettingZooEnv
implementation, but this is less user-friendly and may require in-depth knowledge of both frameworks. A guide or tutorial for integrating custom environments would also be an alternative solution.Additional context
The current setup works well for predefined PettingZoo environments, but adding custom ones could be more intuitive. Enhancing the framework to support easier registration would save time and effort for users extending it with their own environments.
Checklist
The text was updated successfully, but these errors were encountered: