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.
Goal
Enable proper use of the
enableCameraSensors
config parameter.Problem
The current behavior results in
enableCameraSensors
always being False.Reason
enable_camera_sensors = config.get("enableCameraSensors", False)
always returns False because this is reading from the wrong part of the config. In almost all of the task yaml files,enableCameraSensors
is defined undertask.env
, but in the code it is looking undertask
. The use of theget
and default value made this bug pass by silently, but I noticed it when trying to get my camera sensors to work in a headless training environment.I also fixed the AllegroHands' yaml files to be consistent with the others (before they were under
task.task
).How To Check
Can manually check using:
I also wrote a small python script called
check_for_enableCameraSensors.py
that does a similar check if placed inIsaacGymEnvs/isaacgymenvs
.Before Change
Note the ['task, 'task', 'enableCameraSensors'] in AllegroHand is inconsistent (it was the same in AllegroHandManualDR and AllegroHandADR too, but failed to load for some reason).
After
Note the consistent ['task, 'env', 'enableCameraSensors'] now.