Skip to content

Refactor Workcell Bidding + Assignments into respective BT nodes #66

@Yadunund

Description

@Yadunund

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions