-
Notifications
You must be signed in to change notification settings - Fork 0
Code review of RFC - Simulation Interfaces #2
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
Code review of RFC - Simulation Interfaces #2
Conversation
Signed-off-by: Jan Hanca <[email protected]>
Signed-off-by: Jan Hanca <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Reasonable propositions, that organize this document. I made few remarks for discussion, and few nitpicks.
| SCOPE_STATE | Move all spawned entities to initial poses cached in `ROS 2 Entities manager`. | | ||
| SCOPE_TIME | New call using `ROS2Bus` | | ||
## SetSimulationState service |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It may be worth noting here or under GetSimulationState, what will be the initial state? According to simulation interfaces RFC simulation starts as PAUSED.
Moreover, I would at least consider, what is before this? I guess the ROS 2 simulation interfaces become available only when simulation is initialized, and the state is first set to PAUSED.
Signed-off-by: Jan Hanca <[email protected]> Co-authored-by: Michał Pełka <[email protected]> Co-authored-by: Paweł Liberadzki <[email protected]> Signed-off-by: Jan Hanca <[email protected]>
Signed-off-by: Jan Hanca <[email protected]>
This is my code review of #1 . The main goal was to make the text more formal (RFC style) and to make it easier to read by people less familiar with Simulation Interfaces. The changes are focused around the text - they do not really change the meaning of the RFC.
Additionally, the definitions of all ROS 2 interfaces were removed from this RFC, as they are not relevant. The links are left in the text.