-
Notifications
You must be signed in to change notification settings - Fork 2.5k
Adds use_terrain_origins
option to TerrainImporterCfg
#3537
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
base: main
Are you sure you want to change the base?
Adds use_terrain_origins
option to TerrainImporterCfg
#3537
Conversation
Could you please update the changelog and extension.toml file? :) |
Thank you for new feature!! I am curious in what use cases do you want a generated sub terrain but with grid origin :) |
Co-authored-by: Mayank Mittal <[email protected]> Signed-off-by: Georg Wiedebach <[email protected]>
Co-authored-by: Mayank Mittal <[email protected]> Signed-off-by: Georg Wiedebach <[email protected]>
Co-authored-by: Mayank Mittal <[email protected]> Signed-off-by: Georg Wiedebach <[email protected]>
47cbc3a
to
a5e8187
Compare
Appreciate the reviews! I have incremented the version and updated the changelog. @ooctipus some of the policies I train on the generated terrain stay in one place (jump in place, kneel down). This setting allows me to get a good spread of the robots across the "slopes" terrain, for example. Also I think exported videos look much nicer if the robots are not clumped together. |
Description
Support distributing environments in a grid when using a generated terrain.
Fixes #3536
Type of change
Screenshots
Checklist
pre-commit
checks with./isaaclab.sh --format
config/extension.toml
fileCONTRIBUTORS.md
or my name already exists there