-
Notifications
You must be signed in to change notification settings - Fork 410
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Infer entity paths from LeRobot dataset feature metadata #8981
Conversation
Web viewer built successfully. If applicable, you should also test it:
Note: This comment is updated whenever you push a commit. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm!
#[derive(Debug, Serialize, Deserialize)] | ||
#[serde(untagged)] | ||
pub enum Names { | ||
Motors { motors: Vec<String> }, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's not just Motors(Vec<String>)
to reflect what it looks like in the dataset? Otherwise this looks strangely inconsistent to the List(Vec<_>)
below
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nope, I've seen these two variants:
"names": {
"motors": [
"motor_0",
"motor_1",
"motor_2",
"motor_3",
"motor_4",
"motor_5",
"motor_6",
"motor_7"
]
}
or
"names": [
"height",
"width",
"channel"
]
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
sounds like yes this enum is closely mirroring what shows up in the datasets :)
### Related Closes #8969 ### What We now use the feature metadata from the LeRobot dataset to make the entity paths where possible.  (motor names for both observation and action values when visualizing [lerobot/pusht](https://huggingface.co/datasets/lerobot/pusht))
Related
Closes #8969
What
We now use the feature metadata from the LeRobot dataset to make the entity paths where possible.
(motor names for both observation and action values when visualizing lerobot/pusht)