Updates

  • 12/06/17 parallel problems updated
  • 26/05/17 parallel problems released
  • 01/03/17 parallel training problems released
  • 15/02/17 sequential problems released
  • 01/02/17 training sequential up, challenge problems postponed
  • 27/01/17 update on parallel problems

Important Dates:

  • 12/07/17
       RERS at ISSTA/SPIN
  • 01/02/17
       Release Sequential Training    Problems
  • 15/02/17
       Release Sequential    Problems
  • 01/03/17
       Release Parallel Training    Problems
  • 26/05/17
       Release Parallel Problems
  • 01/02/17 - 01/07/17
       Challenge Phase
  • 15/02/17 - 01/07/17
       Solution Submission

How to proceed

To get a feeling for the provided problems, we provide a set of sequential and parallel training problems with solutions that are very similar to those found in the actual challenge, but tend to be smaller in size.

You may proceed as the following:

  • Step 1. Download the problems and properties of the track you want to participate in.
  • Step 2. Read the sequential problem description or parallel problem description. Select your favorite method or tools to find out which properties are satisfied. You may use your own tool or other people's tools or any combination thereof - the challenge is completely free-style. Some prominent tools you may consider to involve are:
    1. SPIN
    2. mCRL2
    3. LTSmin
    4. LearnLib
    If you want your tool to be listed here or if you have any other suggestion for tools, please contact us!
  • Step 3. Test the strengths of your methods or tools using the sequential or parallel training problems.
  • Step 4. Once you are warmed up by working with the training problems, you will be ready for the actual challenge. Repeat Step 1 to Step 3 for the challenge problems. Good luck!
  • Step 5. Submit your solutions within the provided time frame for each category as listed on the left! The submission format is defined on the submission page.
  • Step 6. Receive your evaluation and hopefully also your achievements and rewards during the RERS meeting which in particular also discusses the profile of future RERS problems.

The challenge is free-style. You are allowed to patch the code in any way you like, but the validity has, of course, to be stated according to the original problems. Nevertheless you should first concentrate on the problems and properties you can master well. You do not have to give an answer to all problems. Of course, the more problems you can tackle, the more points you may be able to win, but please be aware, wrong answers have a high penalty!

Concerning the second form of ranking, please write a short summary of your approach, the encountered hurdles, your solutions, and your results. In these summaries, honesty, e.g. also concerning weaknesses of the employed methods, is important. Our challenge aims at profiling the various approaches and methods, which in particular means that weaknesses need to be identified. Of course, we are also very interested in new ideas and solutions that were motivated by the challenge. Details about the ranking or evaluation method can be found here.