Skip to content
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

Merged
merged 1 commit into from
Feb 10, 2025

Conversation

oxkitsune
Copy link
Member

Related

Closes #8969

What

We now use the feature metadata from the LeRobot dataset to make the entity paths where possible.

image
(motor names for both observation and action values when visualizing lerobot/pusht)

@oxkitsune oxkitsune added enhancement New feature or request 📺 re_viewer affects re_viewer itself include in changelog labels Feb 10, 2025
Copy link

github-actions bot commented Feb 10, 2025

Web viewer built successfully. If applicable, you should also test it:

  • I have tested the web viewer
Result Commit Link Manifest
aac99cd https://rerun.io/viewer/pr/8981 +nightly +main

Note: This comment is updated whenever you push a commit.

@Wumpf Wumpf self-requested a review February 10, 2025 12:21
Copy link
Member

@Wumpf Wumpf left a 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> },
Copy link
Member

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

Copy link
Member Author

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"
]

Copy link
Member

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 :)

@oxkitsune oxkitsune merged commit 9a23563 into main Feb 10, 2025
42 checks passed
@oxkitsune oxkitsune deleted the gijs/infer-entity-names branch February 10, 2025 13:07
@oxkitsune oxkitsune mentioned this pull request Feb 19, 2025
@oxkitsune oxkitsune added this to the Next patch release milestone Feb 19, 2025
oxkitsune added a commit that referenced this pull request Feb 19, 2025
### Related

Closes #8969 

### What

We now use the feature metadata from the LeRobot dataset to make the
entity paths where possible.


![image](https://github.com/user-attachments/assets/3b534f21-31db-4e16-8780-b26bc9b1bbd1)
(motor names for both observation and action values when visualizing
[lerobot/pusht](https://huggingface.co/datasets/lerobot/pusht))
@Wumpf Wumpf removed this from the Next patch release milestone Feb 20, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request include in changelog 📺 re_viewer affects re_viewer itself
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Infer entity names from LeRobot feature metadata
2 participants