Release RoboLab-120 on Hugging Face
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 508
- Forks
- 81
- Avg merge
- 14d 21h
- Merged PRs (30d)
- 2
Description
Hi @xuningy 🤗
I'm Niels and work as part of the open-source team at Hugging Face. I discovered your work through Hugging Face's daily papers as yours got featured: https://huggingface.co/papers/2604.09860.
The paper page lets people discuss about your paper and lets them find artifacts about it (your dataset for instance),
you can also claim the paper as yours which will show up on your public profile at HF, add Github and project page URLs.
Would you like to host the RoboLab-120 benchmark and asset libraries you've released on https://huggingface.co/datasets?
I see you're using GitHub for it and mention about 7 GB of assets. Hosting on Hugging Face will give you more visibility/enable better discoverability, and will also allow people to do:
from datasets import load_dataset
dataset = load_dataset("NVLabs/RoboLab")
If you're down, leaving a guide here: https://huggingface.co/docs/datasets/loading.
We support large file storage, which is useful for the USD objects and textures in your framework.
Besides that, there's the dataset viewer which allows people to quickly explore the data in the browser.
After uploaded, we can also link the datasets to the paper page (read here) so people can discover your work.
Let me know if you're interested/need any guidance.
Kind regards,
Niels
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the Hugging Face datasets loading guide and dataset viewer documentation linked in the issue, then review the existing RoboLab benchmark and asset libraries, including the USD objects and textures. Done means hosting the dataset on Hugging Face, making it loadable with the shown Python call, and linking it to the paper page.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data, release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100