Skip to content

Plan-repair (2/3): omniplanner_repair_node with constraint merging via plugin#28

Open
JY-HIM4U wants to merge 1 commit into
feature/planning-constraintsfrom
feature/omniplanner-repair-node
Open

Plan-repair (2/3): omniplanner_repair_node with constraint merging via plugin#28
JY-HIM4U wants to merge 1 commit into
feature/planning-constraintsfrom
feature/omniplanner-repair-node

Conversation

@JY-HIM4U
Copy link
Copy Markdown
Contributor

Adds the omniplanner_repair_node and a constraint-aware plugin that consumes ConstrainedPddlGoalMsg. Persistent constraints flow in through ~/constraints; per-message constraints ride along with the goal. Both are merged into goal.constraints before grounding (the field added in PR 1).
This is 2 of 3 in a stacked series:

  • PR 1: planning-side constraint plumbing (ConstraintFact, ConstrainedPddlGoalMsg, PddlGoal.constraints, grounding-level filtering).
  • PR 2 (this): ROS-level repair node + plugin + plan-info publishing hook.

…a plugin

Avoid duplicating register_plugin; let the plugin do the work.

- omniplanner_msgs: ConstraintList.msg for persistent ~/constraints topic
- omniplanner_node: small extension point — plan_handler calls
  plugin.on_plan_compiled(plans, plan_dict) if defined. Plugins that
  don't define it are unaffected.
- multirobot_ros: new MultiRobotPddlConstrainedPlannerRos plugin
    - subscribes to ConstrainedPddlGoalMsg (from PR 1)
    - merges persistent constraints from node.active_constraints with
      per-message constraints into a PddlGoal.constraints list
    - on_plan_compiled hook publishes per-robot visited POIs to
      /<robot>/omniplanner_node/plan_visited_pois
- omniplanner_repair_node: thin OmniPlannerRos subclass — adds
  ~/constraints topic and active_constraints state. No register_plugin
  override; no plan-handling duplication.
@JY-HIM4U JY-HIM4U force-pushed the feature/planning-constraints branch from 9259fdc to d2332dc Compare May 18, 2026 21:27
@JY-HIM4U JY-HIM4U force-pushed the feature/omniplanner-repair-node branch 2 times, most recently from 99348c9 to 424a366 Compare May 18, 2026 21:28
Copy link
Copy Markdown
Collaborator

@GoldenZephyr GoldenZephyr left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

looks good

@JY-HIM4U JY-HIM4U force-pushed the feature/planning-constraints branch from 4a9cc15 to 90b3b4c Compare May 19, 2026 18:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants