[Feature Request] Make check_env assertions in regard to observation_space more actionable #1399
Closed
1 task done
Labels
enhancement
New feature or request
🚀 Feature
When checking the implementation of a custom gym with
check_env
there are a number of ways to fail the validation.For the
observation_space
, the dtype or the shape could be wrong (as indicated in #746, #921 and #932) that will all lead to the same AssertionError:This is telling the user that something is wrong, but it's not clear what exactly is causing the validation failure.
Out of my head, I could think of two more actionable error messages that would help a user understand what is wrong:
For the wrong shape:
For the wrong dtype:
Arguably there are more failure modes associated with this error.
(Since I ran into this and have assured that the above reasons do not apply)
P.S. If you have suggestions what else can let this assertion fail, I would appreciate that to help me find my issue...
Motivation
No response
Pitch
No response
Alternatives
No response
Additional context
No response
Checklist
The text was updated successfully, but these errors were encountered: