You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Some datasets such as droid define the same key twice (i.e. gripper_position as an action as well as a proprioception).
This leads to the entry of the second key overwriting the first without further warning.
To Reproduce
Steps to reproduce the behavior:
import the droid dataset
try to access both keys after import
you will see, that there is only one left with the values of the key, appearing last (in this case proprioception/gripper_position)
Expected behavior
Both keys should be represented
Suggestion
We patched this problem temporarily, however we should find a long term solution.
See: utn-blei@06ede76
The text was updated successfully, but these errors were encountered:
Describe the bug
Some datasets such as droid define the same key twice (i.e. gripper_position as an action as well as a proprioception).
This leads to the entry of the second key overwriting the first without further warning.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Both keys should be represented
Suggestion
We patched this problem temporarily, however we should find a long term solution.
See: utn-blei@06ede76
The text was updated successfully, but these errors were encountered: