sdformat
sdformat copied to clipboard
gazebosim
Simulation Description Format (SDFormat) parser and description files.
## Desired behavior I hope SDFormat would support the PhysX(Nvidia) as a physic engine so that I can utilize the standard format for robot simulation. Since Nvidia PhysX introduced a...
## Environment * OS Version: Ubuntu 18.04 * Source build of sdf6 branch (since packages are affected by #585 to use ign) * Binaries for sdformat9 9.2.0 ## Description With...
Items to be addressed: - [ ] Support custom elements - [ ] Currently, the `test/integration/param_passing.cc` test uses `include_custom_model.sdf` to test all actions. Actions should be divided in multiple separate...
## Environment * OS Version: Ubuntu 18.04 * Source build, `sdformat11_11.1.0` ## Description * Expected behavior: `WarningsPolicy()` allows us to configure multiple unallowed root-level elements for any model (direct parsing...
## Environment * OS Version: Ubuntu 20.04 * Source build, branch `sdf11` ## Description * Expected behavior: When calling `sdf::findFile` with `test_model/model.sdf` as the input `_filename`, instead of a base...
It has always been my understanding based on the [usage in osrf/gazebo](https://github.com/osrf/gazebo/blob/6fd426b3949c4ca73fa126cde68f5cc4a59522eb/test/worlds/force_torque_frame_test.world#L88-L163) that a sensor of type `force_torque` may only be a `//joint/sensor` and not a `//link/sensor`. I believe it...
Came up here: https://github.com/robotlocomotion/drake/pull/13824#pullrequestreview-462497185 For certain joint types, like `@type="ball"`, it doesn't really make sense to have `//axis/xyz` specified? However, when I look around, sometimes it is, sometimes it isn't?...
**Original report ([archived issue](https://osrf-migration.github.io/sdformat-gh-pages/#!/osrf/sdformat/issues/231)) by Steve Peters (Bitbucket: [Steven Peters](https://bitbucket.org/%7B2ccfed09-18b8-4921-8d58-15ef01092802%7D/), GitHub: [scpeters](https://github.com/scpeters)).** ---------------------------------------- This is a follow-up task from [pr #329](https://osrf-migration.github.io/sdformat-gh-pages/#!/osrf/sdformat/pull-requests/329), which proposed to "Add random walk params to noise...
## Desired behavior To have a standard location for SDFormat files used in integration testing. ## Alternatives considered n/a ## Implementation suggestion I propose we move all SDFormat files used...
## Environment * OS Version: any * Source or binary build? any ## Description * Expected behavior: After using `sdf::Element::Copy`, the source and destination elements should have the same attributes....