2019
DOI: 10.1007/978-3-031-02013-1
|View full text |Cite
|
Sign up to set email alerts
|

Introduction to Distributed Self-Stabilizing Algorithms

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
3
1
1

Citation Types

0
25
0

Year Published

2021
2021
2023
2023

Publication Types

Select...
5
1

Relationship

0
6

Authors

Journals

citations
Cited by 32 publications
(25 citation statements)
references
References 100 publications
0
25
0
Order By: Relevance
“…Indeed, several robots acted simultaneously in our demos. A similar concept regarding activation is known as a locally central daemon in theoretical distributed algorithms [21]. Throughout the article, we assume that each path π i starts from s i and ends at g i to focus on analyses related to schedules.…”
Section: B Rationale and Remarksmentioning
confidence: 99%
“…Indeed, several robots acted simultaneously in our demos. A similar concept regarding activation is known as a locally central daemon in theoretical distributed algorithms [21]. Throughout the article, we assume that each path π i starts from s i and ends at g i to focus on analyses related to schedules.…”
Section: B Rationale and Remarksmentioning
confidence: 99%
“…Since the occurrence of these failures can be arbitrarily combined, we assume these transient-faults can alter the system state in unpredictable ways. In particular, when modeling the system, Dijkstra [15] assumes that these violations bring the system to an arbitrary state from which a self-stabilizing system should recover [3,16]. I.e., Dijkstra requires (i) recovery after the last occurrence of a transient-fault and (ii) once the system has recovered, it must never violate the task requirements.…”
Section: Self-stabilizationmentioning
confidence: 99%
“…I.e., there could be any finite number of transient faults before the last one occurs, which may leave the system in an arbitrary state. Moreover, recovery from an arbitrary system state is demonstrated once all transient faults cease to happen, see [4,15] for details. Memory constraints.…”
Section: Self-stabilizationmentioning
confidence: 99%
“…We refer to these violations and deviations as arbitrary transient-faults and assume that they can corrupt the system state arbitrarily (while keeping the program code intact). Our model assumes that the last arbitrary transient fault occurs before the system execution starts [4,15]. Also, it leaves the system to start in an arbitrary state.…”
Section: Arbitrary Transient-faultsmentioning
confidence: 99%