-
Notifications
You must be signed in to change notification settings - Fork 443
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
Add to documentation: How to create your own/custom environment and sensors? #419
Comments
Thanks for your praise in the framework! And thanks for the feedback! We are actually planning to update the documentation more to give better accessibility for advanced usage, like creating your own models. We will take your feedback into account when we upgrade the documentation. Please stay tuned! In the meantime, there are some available resources that have tried to make robosuite environments easier. For example, our work for procedural generation of tasks using PDDL language. All mujoco related stuff are natively supporting |
Ok, that would be interesting to know, because I also noticed that for at least two environments, the reward is almost always zero, such that the exploration phase takes very long until the task is randomly fulfilled at least once. |
Which environments are you referring to? |
In wipe task, can I use my own table by loading xml? |
The framework appears to be easy to use. But for many use cases, we would like to model our own environment
and our own sensors.
Does anybody have experience with how to create your own environment/add your own sensors and could that be
added to the documentation (with code)?
What was the pipeline to create the existing examples, do they base on known scene description file types such as
.usd
,.urdf
,...?The text was updated successfully, but these errors were encountered: