open-rmf / open-rmf/rmf

[Feature request]: Fire alarm separation for different fleets

Open
#658 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
Python
Stars
438
Forks
89
PR merge metrics
No merged PRs in 30d

Description

Before proceeding, is there an existing issue or discussion for this?
Description

Our current deployment uses one RMF instance for two different buildings and in the event when a fire alarm is triggered for one building, ALL robots will go into parking.

This does not make sense for robots in the other building.

The current msg type for the emergency signal is a boolean message, which does not indicate which building or fleet it is meant for.

But since there is no concept of buildings in RMF, I think a fleet-based approach would be best.

Implementation Considerations

The new emergency message will be

EmergencySignal.msg

string[] fleet_names
bool is_emergency

The fleet_names array allow users to specifc which fleet should react to this signal. And in the scenario where this array is empty, ALL robots will react to the signal.

Alternatives

No response

Additional information

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating EmergencySignal.msg and the current boolean emergency-signal handling. Define how fleet_names selects which robots react, including the empty-array case where all robots respond. Done means a fire alarm for one fleet no longer sends other fleets to parking, with coverage for both targeted and broadcast signals.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
distributed-systems, robotics
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.