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.

Sign up for GitHub

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

Jump to bottom

Infer entity names from LeRobot feature metadata #8969

Closed

oxkitsune opened this issue Feb 7, 2025 · 0 comments · Fixed by #8981

Member

oxkitsune commented Feb 7, 2025

Currently, scalar entities don't use the optional feature names from dataset descriptions, e.g.:

"observation.state": {
    "dtype": "float32",
    "shape": [
        2
    ],
    "names": {
        "motors": [
            "motor_0",
            "motor_1"
        ]
    }
}

we should use these to infer better names for the scalar entities we log.

oxkitsune mentioned this issue

Infer entity paths from LeRobot dataset feature metadata #8981

Merged

oxkitsune added a commit that referenced this issue


          Infer entity paths from LeRobot dataset feature metadata (#8981)

9a23563

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

oxkitsune closed this as completed in #8981

oxkitsune added a commit that referenced this issue


          Infer entity paths from LeRobot dataset feature metadata (#8981)

8d7c7ad

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment