Avoid One's Doom: Finding Cliff-Edge Configurations in Petri Nets

Giann Karlo Aguirre-Samboní
(INRIA and LMF, CNRS and ENS Paris-Saclay, Université Paris-Saclay)
Stefan Haar
(INRIA and LMF, CNRS and ENS Paris-Saclay, Université Paris-Saclay)
Loïc Paulevé
(Univ. Bordeaux, Bordeaux INP, CNRS, LaBRI, UMR5800)
Stefan Schwoon
(INRIA and LMF, CNRS and ENS Paris-Saclay, Université Paris-Saclay)
Nick Würdemann
(Department of Computing Science, University of Oldenburg)

A crucial question in analyzing a concurrent system is to determine its long-run behaviour, and in particular, whether there are irreversible choices in its evolution, leading into parts of the reachability space from which there is no return to other parts. Casting this problem in the unifying framework of safe Petri nets, our previous work has provided techniques for identifying attractors, i.e. terminal strongly connected components of the reachability space, whose attraction basins we wish to determine. Here, we provide a solution for the case of safe Petri nets. Our algorithm uses net unfoldings and provides a map of all of the system's configurations (concurrent executions) that act as cliff-edges, i.e. any maximal extension for those configurations lies in some basin that is considered fatal. The computation turns out to require only a relatively small prefix of the unfolding, just twice the depth of Esparza's complete prefix.

In Pierre Ganty and Dario Della Monica: Proceedings of the 13th International Symposium on Games, Automata, Logics and Formal Verification (GandALF 2022), Madrid, Spain, September 21-23, 2022, Electronic Proceedings in Theoretical Computer Science 370, pp. 178–193.
This work was supported by the DIGICOSME grant ESCAPE DIGICOSME RD 242-ESCAPE-15203 and by the French Agence Nationale pour la Recherche (ANR) in the scope of the project ''BNeDiction'' (grant number ANR-20-CE45-0001).
Published: 20th September 2022.

ArXived at: https://dx.doi.org/10.4204/EPTCS.370.12 bibtex PDF
References in reconstructed bibtex, XML and HTML format (approximated).
Comments and questions to: eptcs@eptcs.org
For website issues: webmaster@eptcs.org