-
-
Notifications
You must be signed in to change notification settings - Fork 105
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
MultithreadedEnvs and Trajectories #920
Comments
In my opinion, in the first option, each container should have the full capacity? The |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm creating this issue to pin down that MultiThreadedEnvs do not currently work.
It steps each inner env in parallel and stores the traces, but there's nothing that can be done with that currently as we would need to store each separate trajectory (in the seminal sense of "trajectory") contiguously in the replay buffer. Right now with the caching implementation, they can only be mixed up in the storage.
Options I see to address that
I clearly prefer the first option, it is straightfoward and probably the most efficient.
The text was updated successfully, but these errors were encountered: