<?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-07-23T07:58:23Z</responseDate>
  <request identifier="1358" metadataPrefix="oai_dc" verb="GetRecord">https://drops.dagstuhl.de/oai</request>
  <GetRecord>
    <record>
      <header>
        <identifier>oai:drops-oai.dagstuhl.de:1358</identifier>
        <datestamp>2024-03-06T10:32:59Z</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>Computing Minimum Spanning Trees with Uncertainty</dc:title>
          <dc:creator>Hoffmann, Michael</dc:creator>
          <dc:creator>Erlebach, Thomas</dc:creator>
          <dc:creator>Krizanc, Danny</dc:creator>
          <dc:creator>Mihal'ák, Matús</dc:creator>
          <dc:creator>Raman, Rajeev</dc:creator>
          <dc:subject>Algorithms and data structures; Current challenges: mobile and net computing</dc:subject>
          <dc:description>We consider the minimum spanning tree problem in a setting where&#13;
   information about the edge weights of the given graph is uncertain.&#13;
   Initially, for each edge $e$ of the graph only a set $A_e$, called&#13;
   an uncertainty area, that contains the actual edge weight&#13;
   $w_e$ is known.  The algorithm can `update' $e$ to obtain the edge&#13;
   weight $w_e in A_e$.  The task is to output the edge set of a&#13;
   minimum spanning tree after a minimum number of updates.  An&#13;
   algorithm is $k$-update competitive if it makes at most $k$ times&#13;
   as many updates as the optimum.  We present a $2$-update&#13;
   competitive algorithm if all areas $A_e$ are open or trivial, which&#13;
   is the best possible among deterministic algorithms.  The condition&#13;
   on the areas $A_e$ is to exclude degenerate inputs for which no&#13;
   constant update competitive algorithm can exist.&#13;
&#13;
   Next, we consider a setting where the vertices of the graph&#13;
   correspond to points in Euclidean space and the weight of an edge&#13;
   is equal to the distance of its endpoints.  The location of each&#13;
   point is initially given as an uncertainty area, and an update&#13;
   reveals the exact location of the point.  We give a general&#13;
   relation between the edge uncertainty and the vertex uncertainty&#13;
   versions of a problem and use it to derive a $4$-update competitive&#13;
   algorithm for the minimum spanning tree problem in the vertex&#13;
   uncertainty model.  Again, we show that this is best possible among&#13;
   deterministic algorithms.</dc:description>
          <dc:publisher>Schloss Dagstuhl – Leibniz-Zentrum für Informatik</dc:publisher>
          <dc:contributor>Michael Hoffmann and Thomas Erlebach and Danny Krizanc and Matús Mihal'ák and Rajeev Raman</dc:contributor>
          <dc:date>2008</dc:date>
          <dc:relation>Is Part Of LIPIcs, Volume 1, 25th International Symposium on Theoretical Aspects of Computer Science (2008)</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.STACS.2008.1358</dc:identifier>
          <dc:identifier>urn:nbn:de:0030-drops-13581</dc:identifier>
          <dc:identifier>https://drops.dagstuhl.de/entities/document/10.4230/LIPIcs.STACS.2008.1358</dc:identifier>
          <dc:language>eng</dc:language>
          <dc:rights>https://creativecommons.org/licenses/by-nd/3.0/legalcode</dc:rights>
        </oai_dc:dc>
      </metadata>
    </record>
  </GetRecord>
</OAI-PMH>
