Mobility Matters
Home›Mobile agents on graphs›Exploration›Graph exploration by a single agent›Exploration by oblivious robots›Exploration by luminous robots

Exploration by luminous robots

Myopic Look–Compute–Move robots with a light of a few colours must visit every node of a ring, grid or torus, and stop or keep visiting; how many robots and colours are needed?

Problem statement and measuresexpand

\(k\) anonymous robots, each with a light that shows one of \(c\) colours, are placed on an anonymous graph \(G=(V,E)\) (a ring, a finite grid or a torus) in an initial configuration designated by the algorithm (positions and colours). Each robot repeats Look–Compute–Move cycles. Look: it sees every node within distance \(\varphi\), with the multiset of colours of the robots on each (so it sees towers, nodes with several robots), and its own colour. Compute: a deterministic function of this snapshot, the same for all robots, gives a new colour and a destination, its own node or a neighbour; the robot sees no identifiers, no ports, and (without chirality) no orientation. Move: it moves there. A fair adversarial scheduler (FSYNC, SSYNC or ASYNC) activates the robots. Terminating exploration: every node is visited by some robot and eventually no robot is enabled. Perpetual exploration: every node is visited infinitely often. With finite \(\varphi\) no algorithm works from every initial configuration, so each result names its initial configurations; some papers also require exclusive executions (no two robots on one node or one edge) or opaque robots, recorded under each result. Measures: the number of robots \(k\) and the number of colours \(c\).

Measures: Robots, number of robots \(k\) needed; Colours, number of colours \(c\) of each light; \(c = 1\) means no usable light (oblivious robots).

Grids, FSYNC, terminating, chirality, \(\varphi = 2\)

verified
Robots: tightColours: tight

With \(\varphi = 2\) and chirality, two robots with two colours, or three oblivious robots, explore a grid and stop under FSYNC.

Assumed (added on the last edge are outlined)

+Graph dynamicsstatic graph+Edge directionundirected+Networkfinite grid+Exploration goalterminating exploration (explore, then stop)+Lights (memory and messages)full light (LUMI): visible to the robot and to the others+Schedulerfully synchronous (FSYNC)+Visibility range\(\varphi = 2\) (results hold for every \(\varphi \ge 2\))+Chiralitycommon chirality (same clockwise direction)+Faultsno faults

Not assumed

Identifiersanonymous: all agents are identical
Formal definitions of this setting
Graph dynamics: static graph
\(G_t=G\) for all \(t\): the edge set never changes.
Edge direction: undirected
\(G=(V,E)\) with \(E\subseteq\binom V2\); every edge can be traversed in both directions.
Network: grid
An \(a \times b\) grid (\(n = ab\) nodes; nodes \((i,j)\), edges between nodes at Manhattan distance one); anonymous, with \(a\) and \(b\) unknown. A robot sees the border of the grid when it is within range, since nodes beyond the border are missing from its snapshot.
Exploration goal: terminating
Every node is visited by at least one robot, and from some time on no robot is enabled (no robot changes its position or colour again).
Lights (memory and messages): luminous
LUMI (luminous robots): each robot has a light with \(c\) colours, set at the end of Compute, persistent across cycles, and visible to the robot itself and to every robot within distance \(\varphi\) Das et al. 2016. It is both memory and message. A Look returns, for every node within distance \(\varphi\), the multiset of colours of the robots on it.
Scheduler: FSYNC
FSYNC: in every round every robot executes one atomic Look–Compute–Move cycle.
Visibility range: \(\varphi=2\)
As for \(\varphi = 1\), but the robot sees every node at distance at most \(\varphi = 2\). An algorithm for \(\varphi = 2\) works for every larger \(\varphi\), since a robot can ignore what lies further away.
Chirality: chirality
All robots agree on the clockwise direction: a snapshot is known up to rotation only (no reflection), so a robot on an axis of symmetry of its view can still tell its two sides apart. Robots still share no North.
Faults: no faults
All agents follow the algorithm forever.
Identifiers: anonymous
All agents run the same deterministic algorithm on the same input; no agent has a label. Formally the label function is constant: \(\mathrm{id}(a)=\mathrm{id}(b)\) for all agents \(a,b\).

What is known

Robots · number of robots \(k\) needed
tight
Two.
lower bound
bottlenecksymmetry breaking
holds when
  • one robot (perpetual-exploration bound that also holds for terminating exploration Nagahama et al. 2022)
introductory—
current best
\(2\)
robots start in a designated formation at a corner of the gridtowers allowed (not exclusive)\(a \ge 2\), \(b \ge 3\)
Colours · number of colours \(c\) of each light; \(c = 1\) means no usable light (oblivious robots)
tight
Two for two robots.
lower bound
bottlenecksymmetry breaking
holds when
  • two robots with one colour, any finite \(\varphi\) (Theorem 2, applied to terminating exploration in Nagahama et al. 2022)
introductory—
current best
\(2\)
robots start in a designated formation at a corner of the gridtowers allowed (not exclusive)\(a \ge 2\), \(b \ge 3\)

Results, in order of publication

Robots \(2\)Colours \(2\)
robots start in a designated formation at a corner of the gridtowers allowed (not exclusive)\(a \ge 2\), \(b \ge 3\)

Introductory; optimal in robots (Section 4.2.1).

Robots \(3\)Colours \(1\)
robots start in a designated formation at a corner of the gridtowers allowed (not exclusive)\(a \ge 2\), \(b \ge 3\)

Oblivious robots (Section 4.2.3); optimal for one colour.

Open questions

None recorded for this variant.

What carries over from neighbouring settings

Read off the order of assumptions, not checked case by case: results may carry extra assumptions (shown on their pages), and asynchronous time is measured in epochs.

Algorithms from weaker settings work here

Lower bounds from stronger settings hold here

No catalogued stronger setting.

Know a better result for this setting, or found a mistake? Suggest a result · Report an error. Accepted contributions are acknowledged.