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

Refactor Workcell Bidding + Assignments into respective BT nodes #66

Open
Tracked by #67
Yadunund opened this issue Jan 24, 2025 · 0 comments
Open
Tracked by #67

Refactor Workcell Bidding + Assignments into respective BT nodes #66

Yadunund opened this issue Jan 24, 2025 · 0 comments
Labels
enhancement New feature or request

Comments

@Yadunund
Copy link
Member

At present when the system orchestrator receives a new Work Order (action goal), it implicitly assigns tasks within the Work Order to available workcells (see here).

However it would be better to refactor this logic into BT nodes for a number of reasons

  1. Improve visibility on what the system orchestrator does by looking at the BT it executes. Right the workcell biding + assignment logic is embedded in the aclcpp_action callbacks within system_orchestrator.cpp while bidding and assigning transporter tasks are explicitly defined in the pick_and_place.xml BT .
  2. To give more freedom to the user on when to bid for workcell assignments. Improve transparency in the main BT to execute by explicitly bundling bidding for workcells and transporters.
  3. As we move towards integrating transporters as workcells, we can reuse these blocks to bid for transporters as well. This would help resolve https://github.com/osrf/nexus/pull/42/files#r1899919027 where a separate BT node was developed that creates a WorkcellTask for transporters and bids within this BT.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant