Skip to content

feat(rmf_plan_executor): allow plan execution with uncommanded robots in fleet - #54

Open
arjo129 wants to merge 1 commit into
arjoc/feat/plan_executor_configurable_gridfrom
arjoc/feat/plan_executor_partial_destinations
Open

feat(rmf_plan_executor): allow plan execution with uncommanded robots in fleet#54
arjo129 wants to merge 1 commit into
arjoc/feat/plan_executor_configurable_gridfrom
arjoc/feat/plan_executor_partial_destinations

Conversation

@arjo129

@arjo129 arjo129 commented Sep 3, 2026

Copy link
Copy Markdown
Member

Bug fix

Builds on #53

Fixed bug

Currently, there is a need for all robots to receive a destination before they execute any plan. This was done initially to make testing consistent while prototyping. However the condition was never removed when

Fix applied

Removed the precondition and allow individual agents to move on their own

It is recommended to use the web based demos to test this new updated functionality.

GenAI Use

We follow OSRA's policy on GenAI tools

  • I used a GenAI tool in this PR.
  • I did not use GenAI

Generated-by: Gemini

… in fleet

- Remove ready_to_execute precondition requiring plans for all robots
- Update bounding_box and trajectory generation to treat uncommanded robots as stationary at latest odometry pose
- Add test_uncommanded_robot_execution unit test

Signed-off-by: Arjo Chakravarty <arjoc@intrinsic.ai>
@mxgrey mxgrey added this to PMC Board Sep 3, 2026
@github-project-automation github-project-automation Bot moved this to Inbox in PMC Board Sep 3, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Inbox

Development

Successfully merging this pull request may close these issues.

2 participants