ROS Index
Repository Summary
| Checkout URI | https://github.com/ros-simulation/simulation_interfaces.git |
| VCS Type | git |
| VCS Version | main |
| Last Updated | 2025-07-29 |
| Dev Status | DEVELOPED |
| Released | RELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Packages
| Name | Version |
|---|---|
| simulation_interfaces | 2.0.0 |
README
Simulation Interfaces
Standard ROS 2 interfaces for interacting with simulators. Messages, services, and actions are documented in their respective files.
Result.msg
The standard includes a generic message for handling service responses, Result.msg, which will likely not be included in the final version of the standard. Since it is generic, it will either be promoted to a common message or included in the service mechanism itself.
Suggested interface implementation priorities
GetSimulatorFeatures should be implemented first, as it provides users with information about the state of support for all standard simulation interfaces.
Following that, aim for maintaining consistency within the implemented feature, such as enabling both Get and Set parts.
Some interfaces represent optional utility and are considered lower priority:
CONTRIBUTING
Repository Summary
| Checkout URI | https://github.com/ros-simulation/simulation_interfaces.git |
| VCS Type | git |
| VCS Version | main |
| Last Updated | 2025-07-29 |
| Dev Status | DEVELOPED |
| Released | RELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Packages
| Name | Version |
|---|---|
| simulation_interfaces | 2.0.0 |
README
Simulation Interfaces
Standard ROS 2 interfaces for interacting with simulators. Messages, services, and actions are documented in their respective files.
Result.msg
The standard includes a generic message for handling service responses, Result.msg, which will likely not be included in the final version of the standard. Since it is generic, it will either be promoted to a common message or included in the service mechanism itself.
Suggested interface implementation priorities
GetSimulatorFeatures should be implemented first, as it provides users with information about the state of support for all standard simulation interfaces.
Following that, aim for maintaining consistency within the implemented feature, such as enabling both Get and Set parts.
Some interfaces represent optional utility and are considered lower priority:
CONTRIBUTING
Repository Summary
| Checkout URI | https://github.com/ros-simulation/simulation_interfaces.git |
| VCS Type | git |
| VCS Version | main |
| Last Updated | 2025-07-29 |
| Dev Status | DEVELOPED |
| Released | RELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Packages
| Name | Version |
|---|---|
| simulation_interfaces | 2.0.0 |
README
Simulation Interfaces
Standard ROS 2 interfaces for interacting with simulators. Messages, services, and actions are documented in their respective files.
Result.msg
The standard includes a generic message for handling service responses, Result.msg, which will likely not be included in the final version of the standard. Since it is generic, it will either be promoted to a common message or included in the service mechanism itself.
Suggested interface implementation priorities
GetSimulatorFeatures should be implemented first, as it provides users with information about the state of support for all standard simulation interfaces.
Following that, aim for maintaining consistency within the implemented feature, such as enabling both Get and Set parts.
Some interfaces represent optional utility and are considered lower priority:
CONTRIBUTING
Repository Summary
| Checkout URI | https://github.com/ros-simulation/simulation_interfaces.git |
| VCS Type | git |
| VCS Version | main |
| Last Updated | 2025-07-29 |
| Dev Status | DEVELOPED |
| Released | RELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Packages
| Name | Version |
|---|---|
| simulation_interfaces | 2.0.0 |
README
Simulation Interfaces
Standard ROS 2 interfaces for interacting with simulators. Messages, services, and actions are documented in their respective files.
Result.msg
The standard includes a generic message for handling service responses, Result.msg, which will likely not be included in the final version of the standard. Since it is generic, it will either be promoted to a common message or included in the service mechanism itself.
Suggested interface implementation priorities
GetSimulatorFeatures should be implemented first, as it provides users with information about the state of support for all standard simulation interfaces.
Following that, aim for maintaining consistency within the implemented feature, such as enabling both Get and Set parts.
Some interfaces represent optional utility and are considered lower priority:
CONTRIBUTING
Repository Summary
| Checkout URI | https://github.com/ros-simulation/simulation_interfaces.git |
| VCS Type | git |
| VCS Version | main |
| Last Updated | 2025-07-29 |
| Dev Status | DEVELOPED |
| Released | RELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Packages
| Name | Version |
|---|---|
| simulation_interfaces | 2.0.0 |
README
Simulation Interfaces
Standard ROS 2 interfaces for interacting with simulators. Messages, services, and actions are documented in their respective files.
Result.msg
The standard includes a generic message for handling service responses, Result.msg, which will likely not be included in the final version of the standard. Since it is generic, it will either be promoted to a common message or included in the service mechanism itself.
Suggested interface implementation priorities
GetSimulatorFeatures should be implemented first, as it provides users with information about the state of support for all standard simulation interfaces.
Following that, aim for maintaining consistency within the implemented feature, such as enabling both Get and Set parts.
Some interfaces represent optional utility and are considered lower priority:
CONTRIBUTING
Repository Summary
| Checkout URI | https://github.com/ros-simulation/simulation_interfaces.git |
| VCS Type | git |
| VCS Version | main |
| Last Updated | 2025-07-29 |
| Dev Status | DEVELOPED |
| Released | RELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Packages
| Name | Version |
|---|---|
| simulation_interfaces | 2.0.0 |
README
Simulation Interfaces
Standard ROS 2 interfaces for interacting with simulators. Messages, services, and actions are documented in their respective files.
Result.msg
The standard includes a generic message for handling service responses, Result.msg, which will likely not be included in the final version of the standard. Since it is generic, it will either be promoted to a common message or included in the service mechanism itself.
Suggested interface implementation priorities
GetSimulatorFeatures should be implemented first, as it provides users with information about the state of support for all standard simulation interfaces.
Following that, aim for maintaining consistency within the implemented feature, such as enabling both Get and Set parts.
Some interfaces represent optional utility and are considered lower priority:
CONTRIBUTING
Repository Summary
| Checkout URI | https://github.com/ros-simulation/simulation_interfaces.git |
| VCS Type | git |
| VCS Version | main |
| Last Updated | 2025-07-29 |
| Dev Status | DEVELOPED |
| Released | RELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Packages
| Name | Version |
|---|---|
| simulation_interfaces | 2.0.0 |
README
Simulation Interfaces
Standard ROS 2 interfaces for interacting with simulators. Messages, services, and actions are documented in their respective files.
Result.msg
The standard includes a generic message for handling service responses, Result.msg, which will likely not be included in the final version of the standard. Since it is generic, it will either be promoted to a common message or included in the service mechanism itself.
Suggested interface implementation priorities
GetSimulatorFeatures should be implemented first, as it provides users with information about the state of support for all standard simulation interfaces.
Following that, aim for maintaining consistency within the implemented feature, such as enabling both Get and Set parts.
Some interfaces represent optional utility and are considered lower priority:
CONTRIBUTING
Repository Summary
| Checkout URI | https://github.com/ros-simulation/simulation_interfaces.git |
| VCS Type | git |
| VCS Version | main |
| Last Updated | 2025-07-29 |
| Dev Status | DEVELOPED |
| Released | RELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Packages
| Name | Version |
|---|---|
| simulation_interfaces | 2.0.0 |
README
Simulation Interfaces
Standard ROS 2 interfaces for interacting with simulators. Messages, services, and actions are documented in their respective files.
Result.msg
The standard includes a generic message for handling service responses, Result.msg, which will likely not be included in the final version of the standard. Since it is generic, it will either be promoted to a common message or included in the service mechanism itself.
Suggested interface implementation priorities
GetSimulatorFeatures should be implemented first, as it provides users with information about the state of support for all standard simulation interfaces.
Following that, aim for maintaining consistency within the implemented feature, such as enabling both Get and Set parts.
Some interfaces represent optional utility and are considered lower priority:
CONTRIBUTING
Repository Summary
| Checkout URI | https://github.com/ros-simulation/simulation_interfaces.git |
| VCS Type | git |
| VCS Version | main |
| Last Updated | 2025-07-29 |
| Dev Status | DEVELOPED |
| Released | RELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Packages
| Name | Version |
|---|---|
| simulation_interfaces | 2.0.0 |
README
Simulation Interfaces
Standard ROS 2 interfaces for interacting with simulators. Messages, services, and actions are documented in their respective files.
Result.msg
The standard includes a generic message for handling service responses, Result.msg, which will likely not be included in the final version of the standard. Since it is generic, it will either be promoted to a common message or included in the service mechanism itself.
Suggested interface implementation priorities
GetSimulatorFeatures should be implemented first, as it provides users with information about the state of support for all standard simulation interfaces.
Following that, aim for maintaining consistency within the implemented feature, such as enabling both Get and Set parts.
Some interfaces represent optional utility and are considered lower priority:
CONTRIBUTING
Repository Summary
| Checkout URI | https://github.com/ros-simulation/simulation_interfaces.git |
| VCS Type | git |
| VCS Version | main |
| Last Updated | 2025-07-29 |
| Dev Status | DEVELOPED |
| Released | RELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Packages
| Name | Version |
|---|---|
| simulation_interfaces | 2.0.0 |
README
Simulation Interfaces
Standard ROS 2 interfaces for interacting with simulators. Messages, services, and actions are documented in their respective files.
Result.msg
The standard includes a generic message for handling service responses, Result.msg, which will likely not be included in the final version of the standard. Since it is generic, it will either be promoted to a common message or included in the service mechanism itself.
Suggested interface implementation priorities
GetSimulatorFeatures should be implemented first, as it provides users with information about the state of support for all standard simulation interfaces.
Following that, aim for maintaining consistency within the implemented feature, such as enabling both Get and Set parts.
Some interfaces represent optional utility and are considered lower priority:
CONTRIBUTING
Repository Summary
| Checkout URI | https://github.com/ros-simulation/simulation_interfaces.git |
| VCS Type | git |
| VCS Version | main |
| Last Updated | 2025-07-29 |
| Dev Status | DEVELOPED |
| Released | RELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Packages
| Name | Version |
|---|---|
| simulation_interfaces | 2.0.0 |
README
Simulation Interfaces
Standard ROS 2 interfaces for interacting with simulators. Messages, services, and actions are documented in their respective files.
Result.msg
The standard includes a generic message for handling service responses, Result.msg, which will likely not be included in the final version of the standard. Since it is generic, it will either be promoted to a common message or included in the service mechanism itself.
Suggested interface implementation priorities
GetSimulatorFeatures should be implemented first, as it provides users with information about the state of support for all standard simulation interfaces.
Following that, aim for maintaining consistency within the implemented feature, such as enabling both Get and Set parts.
Some interfaces represent optional utility and are considered lower priority:
CONTRIBUTING
Repository Summary
| Checkout URI | https://github.com/ros-simulation/simulation_interfaces.git |
| VCS Type | git |
| VCS Version | main |
| Last Updated | 2025-07-29 |
| Dev Status | DEVELOPED |
| Released | RELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Packages
| Name | Version |
|---|---|
| simulation_interfaces | 2.0.0 |
README
Simulation Interfaces
Standard ROS 2 interfaces for interacting with simulators. Messages, services, and actions are documented in their respective files.
Result.msg
The standard includes a generic message for handling service responses, Result.msg, which will likely not be included in the final version of the standard. Since it is generic, it will either be promoted to a common message or included in the service mechanism itself.
Suggested interface implementation priorities
GetSimulatorFeatures should be implemented first, as it provides users with information about the state of support for all standard simulation interfaces.
Following that, aim for maintaining consistency within the implemented feature, such as enabling both Get and Set parts.
Some interfaces represent optional utility and are considered lower priority:
CONTRIBUTING
Repository Summary
| Checkout URI | https://github.com/ros-simulation/simulation_interfaces.git |
| VCS Type | git |
| VCS Version | main |
| Last Updated | 2025-07-29 |
| Dev Status | DEVELOPED |
| Released | RELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Packages
| Name | Version |
|---|---|
| simulation_interfaces | 2.0.0 |
README
Simulation Interfaces
Standard ROS 2 interfaces for interacting with simulators. Messages, services, and actions are documented in their respective files.
Result.msg
The standard includes a generic message for handling service responses, Result.msg, which will likely not be included in the final version of the standard. Since it is generic, it will either be promoted to a common message or included in the service mechanism itself.
Suggested interface implementation priorities
GetSimulatorFeatures should be implemented first, as it provides users with information about the state of support for all standard simulation interfaces.
Following that, aim for maintaining consistency within the implemented feature, such as enabling both Get and Set parts.
Some interfaces represent optional utility and are considered lower priority:
CONTRIBUTING
Repository Summary
| Checkout URI | https://github.com/ros-simulation/simulation_interfaces.git |
| VCS Type | git |
| VCS Version | main |
| Last Updated | 2025-07-29 |
| Dev Status | DEVELOPED |
| Released | RELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Packages
| Name | Version |
|---|---|
| simulation_interfaces | 2.0.0 |
README
Simulation Interfaces
Standard ROS 2 interfaces for interacting with simulators. Messages, services, and actions are documented in their respective files.
Result.msg
The standard includes a generic message for handling service responses, Result.msg, which will likely not be included in the final version of the standard. Since it is generic, it will either be promoted to a common message or included in the service mechanism itself.
Suggested interface implementation priorities
GetSimulatorFeatures should be implemented first, as it provides users with information about the state of support for all standard simulation interfaces.
Following that, aim for maintaining consistency within the implemented feature, such as enabling both Get and Set parts.
Some interfaces represent optional utility and are considered lower priority:
CONTRIBUTING
Repository Summary
| Checkout URI | https://github.com/ros-simulation/simulation_interfaces.git |
| VCS Type | git |
| VCS Version | main |
| Last Updated | 2025-07-29 |
| Dev Status | DEVELOPED |
| Released | RELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Packages
| Name | Version |
|---|---|
| simulation_interfaces | 2.0.0 |
README
Simulation Interfaces
Standard ROS 2 interfaces for interacting with simulators. Messages, services, and actions are documented in their respective files.
Result.msg
The standard includes a generic message for handling service responses, Result.msg, which will likely not be included in the final version of the standard. Since it is generic, it will either be promoted to a common message or included in the service mechanism itself.
Suggested interface implementation priorities
GetSimulatorFeatures should be implemented first, as it provides users with information about the state of support for all standard simulation interfaces.
Following that, aim for maintaining consistency within the implemented feature, such as enabling both Get and Set parts.
Some interfaces represent optional utility and are considered lower priority:
CONTRIBUTING
Repository Summary
| Checkout URI | https://github.com/ros-simulation/simulation_interfaces.git |
| VCS Type | git |
| VCS Version | main |
| Last Updated | 2025-07-29 |
| Dev Status | DEVELOPED |
| Released | RELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Packages
| Name | Version |
|---|---|
| simulation_interfaces | 2.0.0 |
README
Simulation Interfaces
Standard ROS 2 interfaces for interacting with simulators. Messages, services, and actions are documented in their respective files.
Result.msg
The standard includes a generic message for handling service responses, Result.msg, which will likely not be included in the final version of the standard. Since it is generic, it will either be promoted to a common message or included in the service mechanism itself.
Suggested interface implementation priorities
GetSimulatorFeatures should be implemented first, as it provides users with information about the state of support for all standard simulation interfaces.
Following that, aim for maintaining consistency within the implemented feature, such as enabling both Get and Set parts.
Some interfaces represent optional utility and are considered lower priority:
CONTRIBUTING
Repository Summary
| Checkout URI | https://github.com/ros-simulation/simulation_interfaces.git |
| VCS Type | git |
| VCS Version | main |
| Last Updated | 2025-07-29 |
| Dev Status | DEVELOPED |
| Released | RELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Packages
| Name | Version |
|---|---|
| simulation_interfaces | 2.0.0 |
README
Simulation Interfaces
Standard ROS 2 interfaces for interacting with simulators. Messages, services, and actions are documented in their respective files.
Result.msg
The standard includes a generic message for handling service responses, Result.msg, which will likely not be included in the final version of the standard. Since it is generic, it will either be promoted to a common message or included in the service mechanism itself.
Suggested interface implementation priorities
GetSimulatorFeatures should be implemented first, as it provides users with information about the state of support for all standard simulation interfaces.
Following that, aim for maintaining consistency within the implemented feature, such as enabling both Get and Set parts.
Some interfaces represent optional utility and are considered lower priority:
CONTRIBUTING
Repository Summary
| Checkout URI | https://github.com/ros-simulation/simulation_interfaces.git |
| VCS Type | git |
| VCS Version | main |
| Last Updated | 2025-07-29 |
| Dev Status | DEVELOPED |
| Released | RELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Packages
| Name | Version |
|---|---|
| simulation_interfaces | 2.0.0 |
README
Simulation Interfaces
Standard ROS 2 interfaces for interacting with simulators. Messages, services, and actions are documented in their respective files.
Result.msg
The standard includes a generic message for handling service responses, Result.msg, which will likely not be included in the final version of the standard. Since it is generic, it will either be promoted to a common message or included in the service mechanism itself.
Suggested interface implementation priorities
GetSimulatorFeatures should be implemented first, as it provides users with information about the state of support for all standard simulation interfaces.
Following that, aim for maintaining consistency within the implemented feature, such as enabling both Get and Set parts.
Some interfaces represent optional utility and are considered lower priority:
CONTRIBUTING
Repository Summary
| Checkout URI | https://github.com/ros-simulation/simulation_interfaces.git |
| VCS Type | git |
| VCS Version | main |
| Last Updated | 2025-07-29 |
| Dev Status | DEVELOPED |
| Released | RELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Packages
| Name | Version |
|---|---|
| simulation_interfaces | 2.0.0 |
README
Simulation Interfaces
Standard ROS 2 interfaces for interacting with simulators. Messages, services, and actions are documented in their respective files.
Result.msg
The standard includes a generic message for handling service responses, Result.msg, which will likely not be included in the final version of the standard. Since it is generic, it will either be promoted to a common message or included in the service mechanism itself.
Suggested interface implementation priorities
GetSimulatorFeatures should be implemented first, as it provides users with information about the state of support for all standard simulation interfaces.
Following that, aim for maintaining consistency within the implemented feature, such as enabling both Get and Set parts.
Some interfaces represent optional utility and are considered lower priority: