I HAVE TO REBASE. ros docker integration#699
Conversation
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
| enable_joystick=args.joystick, | ||
| enable_camera=args.camera, | ||
| enable_connection=os.getenv("ROBOT_IP") is not None, | ||
| enable_ros_bridge=True, | ||
| ) | ||
| robot.start() | ||
|
|
||
| # test navigation | ||
| pose = PoseStamped( | ||
| ts=time.time(), | ||
| frame_id="map", | ||
| position=Vector3(1.0, 1.0, 0.0), | ||
| orientation=Quaternion(0.0, 0.0, 0.0, 1.0), | ||
| ) | ||
|
|
||
| time.sleep(2) | ||
| robot.navigate_to_goal(pose, blocking=False) | ||
|
|
||
| time.sleep(5) | ||
| robot.cancel_navigation() |
There was a problem hiding this comment.
Avoid issuing navigation goal by default in main()
The main() routine now unconditionally constructs a PoseStamped and calls robot.navigate_to_goal(...) followed by robot.cancel_navigation() immediately after robot.start(). Running this script will therefore command the robot to drive toward (1.0, 1.0, 0.0) every time the process starts, even when the user only intended to bring the system up or teleoperate it. The previous version did not send any motion commands at startup. This implicit goal is surprising and risks unintended robot motion; it should be removed or gated behind an explicit CLI flag.
Useful? React with 👍 / 👎.
544f62f to
450662c
Compare
|
Closed in favor of #700 |
No description provided.