import myosuite before sb3 to ensure envs are registered #270
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
BUGFIX: Fix object-target proximity threshold
2.8.3 release
BUGFIX: Manipulation ENV
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
For some SLURM/HPC setups, the registered MyoSuite envs are not recognised correctly when using Hydra.
In particular, the job terminates with error "gymnasium.error.NameNotFound: Environment ... doesn't exist".
This can be fixed by importing myosuite in the sb3_job_script.py before sb3 (which loads gymnasium) is imported.
I have not tested whether the same issue occurs when using torchrl_job_script.py, but a similar fix may be required.