Home > Publications
Home University of Twente
Prospective Students
Intranet (internal)

EEMCS EPrints Service

22550 Multi-core and/or symbolic model checking
Home Policy Brochure Browse Search User Area Contact Help

van Dijk, T. and Laarman, A.W. and van de Pol, J.C. (2012) Multi-core and/or symbolic model checking. (Invited) In: 12th International Workshop on Automated Verification of Critical Systems, AVoCS 2012, 18-20 Sep 2012, Bamberg, Germany. 773:1-773:7. Electronic Communications of the EASST 53. EASST. ISSN 1863-2122

Full text available as:


189 Kb
Open Access

Official URL:

Exported to Metis


We review our progress in high-performance model checking. Our multi-core model checker is based on a scalable hash-table design and parallel random-walk traversal. Our symbolic model checker is based on Multiway Decision Diagrams and the saturation strategy. The LTSmin tool is based on the PINS architecture, decoupling model checking algorithms from the input specification language. Consequently, users can stay in their own specification language and postpone the choice between parallel or symbolic model checking. We support widely different specification languages including those of SPIN (Promela), mCRL2 and UPPAAL (timed automata). So far, multi-core and symbolic algorithms had very little in common, forcing the user in the end to make a wise trade-off between memory or speed. Recently, however, we designed a novel multi-core BDD package called Sylvan. This forms an excellent basis for scalable parallel symbolic model checking.

Item Type:Conference or Workshop Paper (Full Paper, Invited/Keynote Talk)
Research Group:EWI-FMT: Formal Methods and Tools
Research Program:CTIT-DSN: Dependable Systems and Networks
Research Project:CEDICT: 3TU Center of Excellence for ICT
Uncontrolled Keywords:multi-core model checking, symbolic model checking, scalability, hashtable, Binary Decision Diagrams, parallel algorithms
ID Code:22550
Deposited On:12 December 2012
More Information:statisticsmetis

Export this item as:

To correct this item please ask your editor

Repository Staff Only: edit this item