Rigorous Examination of Reactive Systems (RERS)

The RERS Challenge 2017 is the 7th International Challenge on the Rigorous 
Examination of Reactive Systems and is co-located with the SPIN Symposium 2017. 
The event will be held on July 12th 2017 in Santa Barbara, California, USA. 
RERS is designed to encourage software developers and researchers to apply and 
combine their tools and approaches in a freestyle manner to answer evaluation 
questions for reachability and LTL formulas on specifically designed 
benchmarks. The goal of this challenge is to provide a basis for the comparison 
of verification techniques and available tools.

For more information please visit: http://www.rers-challenge.org/2017.

The Challenge

The challenge consists of two types of problems, sequential problems and 
parallel problems, each with increasing difficulty.

  *   The sequential 
problems<http://www.rers-challenge.org/2017/index.php?page=problemDescS> are 
made available as both Java and C sources.
  *   The parallel 
problems<http://www.rers-challenge.org/2017/index.php?page=problemDescP> are 
made available as Petri nets (PNML), Promela specifications (PML), and graphs 
(dot).

Your solutions can be submitted until July 1, through 
http://www.rers-challenge.org/2017/index.php?page=submit. Participants are 
invited to shortly present their approach at the RERS meeting on July 12. This 
year, we have several 250 Euro gift certificates for Springer books, sponsored 
by Springer available. The prices will be distributed among five different 
categories:

  1.  best conceptual method for the sequential problems,
  2.  best conceptual method for the parallel problems,
  3.  highest score in reachability for sequential problems,
  4.  highest score in LTL for sequential problems, and
  5.  highest score in LTL for parallel problems.

To be eligible to win in the first two categories, a two page description sent 
via e-mail<mailto:[email protected]>, of the employed method is required.

For both types of problems we have training data as well. This allows every 
participant to check the correctness of their approach before submitting their 
solution.

Important Dates

  *   01/02/17: Release of sequential training problems
  *   15/02/17: Release of sequential problems, and properties
  *   01/03/17: Release of parallel training problems
  *   01/05/17: Release of parallel problems, and properties
  *   01/02/17 - 01/07/17: Challenge Phase
  *   15/02/17 - 01/07/17: Submission of solutions
  *   12/07/17: Presentation of results at the Spin Symposium

RERS 2017 Organizers

  *   Scientific committee:
     *   Falk Howar, Institute for Applied Software Systems Engineering, Germany
     *   Markus Schordan, Lawrence Livermore National Laboratory, CA, USA
     *   Bernhard Steffen, Technische Universität Dortmund, Germany
     *   Jaco van de Pol, University of Twente, the Netherlands
  *   Benchmark generation committee:
     *   Maren Geske, Technische Universität Dortmund, Germany
     *   Marc Jasper, Technische Universität Dortmund, Germany
  *   Publicity committee:
     *   Jeroen Meijer, University of Twente, the Netherlands

Contact

For any questions and inquiries, please contact us at 
[email protected]<mailto:[email protected]>.

If you wish to receive news and important information about the current 
challenge you can subscribe to our announcement google 
group<https://groups.google.com/forum/#!forum/rers-announce>! Upcoming 
challenges or changes to deadlines will be broadcast over this group. If you 
wish to give feedback on the challenge, or discuss what should be part of 
future challenges you can subscribe to our discussion google 
group<https://groups.google.com/forum/#!forum/rers-discussion>!?

----
[[ Petri Nets World:                                                ]]
[[              http://www.informatik.uni-hamburg.de/TGI/PetriNets/ ]]
[[ Mailing list FAQ:                                                ]]
[[ http://www.informatik.uni-hamburg.de/TGI/PetriNets/pnml/faq.html ]]
[[ Post messages/summary of replies:                                ]]
[[                               [email protected] ]]

Reply via email to