Pin MuJoCo for LIBERO rendering compatibility#140
Open
JiahuiKChen wants to merge 1 commit intoLifelong-Robot-Learning:masterfrom
Open
Pin MuJoCo for LIBERO rendering compatibility#140JiahuiKChen wants to merge 1 commit intoLifelong-Robot-Learning:masterfrom
JiahuiKChen wants to merge 1 commit intoLifelong-Robot-Learning:masterfrom
Conversation
This file contains hidden or 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
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.
Summary
Pin
mujoco==3.3.2inrequirements.txt.Issue Fixed
I encountered issues using LIBERO with MuJoCo > 3.3.2, where eval-time rendering of images appear different from the original training images. Floors appear darker and introducing a distribution shift, causing evaluation success rate degredation.
Issue #88 reports the same thing: that MuJoCo 3.3.3 changes LIBERO-Object rendering, making floors appear darker.
Issue #87 shows similar image rendering issues.
The workaround is to downgrade to MuJoCo 3.3.2, which seems to restore the original rendering. Since this repo already pins related simulation dependencies such as
robosuite==1.4.0, pinning MuJoCo here keeps evaluation environments reproducible.Fixes #88.
Pinning choice
This PR uses a hard pin to
mujoco==3.3.2because this version seemed to fixed my evaluation issues and was also the fix in Issue #88 .If the authors/maintainers know the exact MuJoCo version used to generate the training data, pinning that version would be the best.
Validation