Skip to content
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

Extend state point with velocity, acceleration, orientation and orientation rate #748

Open
denotte opened this issue Dec 14, 2023 · 0 comments

Comments

@denotte
Copy link

denotte commented Dec 14, 2023

Describe the feature

The message StatePoint should be extended by fields for velocity, acceleration, orientation and orientation rate.

To sufficiently express a planned trajectory as created by a route planer we need to communicate time, position, orientation, acceleration, orientation and orientation rate. The proposed changes cover the minimum we found to be necessary for a cosimulation of a route planer and an environment simulation to communicate the resulting trajectory of the planing software using OSI.

Describe alternatives you have considered

The existing message MotionRequest fits the use case quiete well. But the current implementation for the trajectory only covers time, position and orientation.

Describe the backwards compatibility

The proposed change adds optional fields to an existing message. No issues with backwards compatibility expected.

denotte pushed a commit to denotte/open-simulation-interface that referenced this issue Dec 14, 2023
refers to OpenSimulationInterface#748
Extends the StatePoint with optional fields velocity,
acceleration, orientation and orientation rate.

Signed-off-by: Dennis Otte <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant