<?xml version="1.0" encoding="UTF-8"?>
<OAI-PMH xmlns="http://www.openarchives.org/OAI/2.0/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.openarchives.org/OAI/2.0/ http://www.openarchives.org/OAI/2.0/OAI-PMH.xsd">
  <responseDate>2026-08-21T18:34:58Z</responseDate>
  <request identifier="27403" metadataPrefix="oai_dc" verb="GetRecord">https://drops.dagstuhl.de/oai</request>
  <GetRecord>
    <record>
      <header>
        <identifier>oai:drops-oai.dagstuhl.de:27403</identifier>
        <datestamp>2026-08-21T14:42:38Z</datestamp>
        <setSpec>ddc:004</setSpec>
        <setSpec>open_access</setSpec>
      </header>
      <metadata>
        <oai_dc:dc xmlns:oai_dc="http://www.openarchives.org/OAI/2.0/oai_dc/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.openarchives.org/OAI/2.0/oai_dc/ http://www.openarchives.org/OAI/2.0/oai_dc.xsd">
          <dc:title>Computational Power of Energy-Constrained Autonomous Robots Under Sequential Schedulers</dc:title>
          <dc:creator>Feletti, Caterina</dc:creator>
          <dc:creator>Flocchini, Paola</dc:creator>
          <dc:creator>Santoro, Nicola</dc:creator>
          <dc:subject>Autonomous mobile robots</dc:subject>
          <dc:subject>Look-Compute-Move</dc:subject>
          <dc:subject>Computational power</dc:subject>
          <dc:subject>Sequential schedulers</dc:subject>
          <dc:subject>Energy-constrained</dc:subject>
          <dc:description>We consider the distributed framework of swarms of mobile robots. A swarm is a set of computational, anonymous, indistinguishable, homogeneous, and autonomous entities that operate in the Euclidean plane through infinite sequences of Look-Compute-Move cycles. The goal of a swarm is to collaborate to solve a given problem. The ability to solve a problem depends on the swarm features and its setting X^S, where X ∈ {OBLOT, FSTA, FCOM, LUMI} denotes the memory/communication model and S denotes the class of schedulers (e.g., fully-synchronous, sequential, asynchronous) that activate the robots. Given a pool of settings, prior research has characterized the relations (dominance, equivalence, or orthogonality) among their computational powers, recently extending this analysis to the class of sequential schedulers (i.e., activating only one robot per round), and of the restricted ones (i.e., never activating a robot twice consecutively).&#13;
In this paper, we extend the study on sequential schedulers (SEQ, PERM, and RROBIN) by defining two classes of sequential restricted schedulers R-SEQ and R-PERM. In particular, we analyze how the computational power of each model OBLOT, LUMI, and FCOM is affected by considering both sequential schedulers and their restricted variants; for FSTA, we only provide the relation between RROBIN and R-PERM. We establish both equivalence and dominance results: some settings are computationally equivalent, while others can be separated by problems solvable in one setting but not in the other.</dc:description>
          <dc:publisher>Schloss Dagstuhl – Leibniz-Zentrum für Informatik</dc:publisher>
          <dc:contributor>Caterina Feletti and Paola Flocchini and Nicola Santoro</dc:contributor>
          <dc:date>2026</dc:date>
          <dc:relation>Is Part Of LIPIcs, Volume 386, 51st International Symposium on Mathematical Foundations of Computer Science (MFCS 2026)</dc:relation>
          <dc:type>InProceedings</dc:type>
          <dc:type>Text</dc:type>
          <dc:type>doc-type:ResearchArticle</dc:type>
          <dc:type>publishedVersion</dc:type>
          <dc:format>application/pdf</dc:format>
          <dc:identifier>doi:10.4230/LIPIcs.MFCS.2026.22</dc:identifier>
          <dc:identifier>urn:nbn:de:0030-drops-274038</dc:identifier>
          <dc:identifier>https://drops.dagstuhl.de/entities/document/10.4230/LIPIcs.MFCS.2026.22</dc:identifier>
          <dc:language>eng</dc:language>
          <dc:rights>https://creativecommons.org/licenses/by/4.0/legalcode</dc:rights>
        </oai_dc:dc>
      </metadata>
    </record>
  </GetRecord>
</OAI-PMH>
