Difference between revisions of "Termination Competition 2014"

From Termination-Portal.org
Jump to navigationJump to search
 
(50 intermediate revisions by 5 users not shown)
Line 1: Line 1:
 
In 2014, the Termination Competition will be part of the [http://vsl2014.at/olympics/ FLoC Olympic Games].
 
In 2014, the Termination Competition will be part of the [http://vsl2014.at/olympics/ FLoC Olympic Games].
  
== Dates (tentative) ==
+
== Current News ==
  
* call for solvers, certifiers, benchmarks: May 20
+
Competition results at [http://nfa.imn.htwk-leipzig.de/termcomp-2014/competition/20] . Demonstration results  at [http://nfa.imn.htwk-leipzig.de/termcomp-2014/competition/23]. [[Termination Competition 2014 Questionnaire]]. Also, check the mailing list [http://lists.lri.fr/pipermail/termtools/2014-July/thread.html]
* registration of solvers: June 15
+
 
* updates of registered solvers, submission of benchmarks: July 1
+
== Dates ==
* competition runs: July 15 - 20
+
 
* results announced: July 21, during FLoC Olympic Games Award Ceremony, Vienna.
+
* call for tools, certifiers, problems: May 26
 +
* registration of tools: June 15
 +
* updates of registered tools, submission of problems: July 1
 +
* competition runs: July 19 - 21
 +
* results announced: July 21, during the Second FLoC Olympic Games Award Ceremony, Vienna.
  
 
== Competition Categories and Awards ==
 
== Competition Categories and Awards ==
  
The competition contains several categories, grouped in meta-categories:
+
The competition contains several categories, grouped in three meta-categories:
  
* termination of term rewriting (all categories with HO/FO-TRS, with- or without strategies)
+
* termination of term rewriting (all categories with HO/FO-TRSs, with- or without strategies)
 
* complexity analysis of term rewriting (all complexity categories)
 
* complexity analysis of term rewriting (all complexity categories)
* termination in programming languages (Logic Programming, Haskell, Java, C, ...)
+
* termination of programming languages (Logic Programming, Haskell, Java, C, ...)
  
 
In each meta-category, a medal will be awarded to the highest-scoring solver.
 
In each meta-category, a medal will be awarded to the highest-scoring solver.
Line 23: Line 27:
  
 
This puts the emphasis on categories with many competitors.
 
This puts the emphasis on categories with many competitors.
(In particular, a category with just one entrant will produce zero score.)
+
(In particular, a category with just one entrant would produce a zero score.)  
 +
A category is only run at the competition if there are at least 2 participants and at least 40 examples
 +
for this category in the underlying termination problem data base.
 +
 
 +
== New Categories ==
 +
 
 +
This year a new category on termination of C programs will be included (see the details [http://www.termination-portal.org/wiki/C_Programs here]).
 +
 
 +
Other categories for "transition systems" or "large scale (Java) programs" are under consideration depending on the number of interested participants and available problems.
 +
 
 +
== Competition Procedure ==
 +
 
 +
All participants in the same category will be run on a [http://www.termination-portal.org/wiki/Termination_Competition_Problem_Selection_Algorithm subset] of the existing problems of this category. The number of problems used in the competition is not fixed and will depend on the number of existing problems. The problem selection algorithm will be the same as in previous years (link http://www.termination-portal.org/wiki/Termination_Competition_Problem_Selection_Algorithm), however because of moving to [http://www.starexec.org StarExec], there might be modifications of the rules suggested by the organizer and decided by the SC.
 +
 
 +
The wall-clock timeout will be 60 (up to 300) seconds, and 4 cores will be available (if a tool wants to use concurrent execution).
 +
 
 +
For nearly all categories, the tools will be started in their directory and obtain two parameters:
 +
 
 +
* the problem file and
 +
* the timeout in seconds. - UPDATE Thu Jun 12 16:56:23 CEST 2014: one parameter (problem file name) on the command line, extra info from environment variables, see [[Termination Competition 2014 technical details]]
 +
 
 +
The tools are expected to give an answer (YES, NO, MAYBE) in the first line on stdout, followed by a proof in ASCII, HTML, or CPF format. Exceptions to these rules are the [http://www.termination-portal.org/wiki/Termination_Competition_Certified_Categories_Competition certified] (see also the [http://cl-informatik.uibk.ac.at/software/cpf/ CPF-website]) and [http://cl-informatik.uibk.ac.at/users/georg/cbr/competition/ complexity] categories. See all existing [http://www.termination-portal.org/wiki/Category:Categories categories] for more details.
 +
 
 +
For those problems where a correct answer is (partially) known, any contradictory answer will be penalized with a high negative score. Moreover, those buggy systems may have the opportunity to provide a corrected version that will be run again after the end of the live execution (displaying the new results afterwards, but out of competition).
 +
 
 +
For those categories devoted to prove only termination or non-termination, the score of a tool is the number of non-contradictory answers minus the given penalization (if any).
  
 
== Committees ==
 
== Committees ==
Line 29: Line 58:
 
Steering Committee
 
Steering Committee
 
* Jürgen Giesl, RWTH Aachen, Germany
 
* Jürgen Giesl, RWTH Aachen, Germany
* Frederic Mesnard, Reunion
+
* Frederic Mesnard, Université de la Réunion, France
 
* Albert Rubio (chair), UPC Barcelona, Spain
 
* Albert Rubio (chair), UPC Barcelona, Spain
 
* Rene Thiemann, Universität Innsbruck, Austria
 
* Rene Thiemann, Universität Innsbruck, Austria
Line 38: Line 67:
 
* Stefan von der Krone, HTWK Leipzig, Germany
 
* Stefan von der Krone, HTWK Leipzig, Germany
  
== Registration info (tentative) ==
+
== Registration ==
  
Participants must register on Starexec, and by email to the organizer, indicating the competition categories where they plan to enter solvers and benchmarks, and then upload their contributions to starexec.
+
Participants must register on [https://www.starexec.org/starexec/public/registration.jsp StarExecRegistration], indicating the competition categories where they plan to enter tools and problems, and then upload their contributions to [http://www.starexec.org StarExec].
  
We recommended to register early. After the deadline, access to Starexec might be restricted. We need time to prepare the competition, and other competitions may be running in parallel.
+
Note: if I (J. Waldmann) don't know you ("knowing" is roughly symmetrical), then I will ask you to specify: what termination tool you're working on, what competition categories you plan to take part in, your affiliation (in case you're a student,  also the name of your  advisor/research group leader). The email address you give in the registration should be your institutional one.
  
It is highly recommended that participants also subscribe to [http://lists.lri.fr/mailman/listinfo/termtools termtools] because that is where announcements will be made, and discussion takes place.
+
We recommend to register early. After the deadline, access to [http://www.starexec.org StarExec] might be restricted. We need time to prepare the competition, and other competitions may be running in parallel.
  
== Technical Detail ==
+
It is highly recommended that participants also subscribe to the [http://lists.lri.fr/mailman/listinfo/termtools termtools] mailing list, because that is where announcements will be made, and where discussion takes place.
 +
 
 +
== Registration (Detail) ==
 +
 
 +
see this page: [[Termination Competition 2014 Registration]]
 +
 
 +
== StarExec Wiki ==
  
(this sub-page should move to a separate page)
+
Lots of useful information about StarExec is available [https://wiki.uiowa.edu/display/stardev/User+Guide here].
  
We intend to run the competition on [http://www.starexec.org/  StarExec] - a cross-community solver execution and benchmark library service under joint development (since 2012) at the University of Iowa and the University of Miami. Its goal is to facilitate the experimental evaluation of logic solvers and other automated reasoning tools by providing a shared storage and computing infrastructure to store, manage and make available benchmark libraries; execute comparative evaluations; and run solver competitions.
+
== Technical Detail ==
  
For displaying the results of the termination competition, we are building a separate web service at HTWK Leipzig.
+
We intend to run the competition on [http://www.starexec.org/  StarExec] - a cross-community solver (tool) execution and benchmark (problem) library service under joint development (since 2012) at the University of Iowa and the University of Miami.
  
Here is some information for participants:
+
Technical details about the execution platform can be found [http://www.termination-portal.org/wiki/Termination_Competition_2014_technical_details here].
  
* submit solvers for testing the platform [http://lists.lri.fr/pipermail/termtools/2014-February/000940.html]
+
== Contact ==
* how to register on starexec [http://lists.lri.fr/pipermail/termtools/2014-February/000943.html] NOTE: there may be service interruptions (e.g., sudden changes in benchmark arrangement).
 
* STAREXEC_MAX_MEM only 750 MB? [http://lists.lri.fr/pipermail/termtools/2014-February/000941.html] (UPDATE: this was out of date, the limit is actually 64 GB)
 
* Beware if your solver writes to stderr. The "postprocessor" (that expects YES|NO in the first line, for termination) gets to see stdout and stderr merged. If you have trace/log output, you can only show it after the actual answer.
 
* hardware on starexec: see [https://www.starexec.org/starexec/public/machine-specs.txt] Solvers are run on nodes with 4 cores each.
 
* software on starexec: RHEL 6.3 (so [http://mirror.nsc.liu.se/centos-store/6.3/isos/x86_64/ Centos 6.3] should be a close match). Package selection, see [http://starexec.forumotion.com/t23-problem-with-dynamic-linking#47]
 
* java is available on starexec nodes (jdk 1.6.0_41) - see [http://starexec.forumotion.com/t27-install-more-recent-jre-on-nodes] - see also remark on ulimits and -Xmx [http://starexec.forumotion.com/t34-ulimits-settings-may-hurt-java-programs#69]
 
* it is helpful to follow other solver communities, e.g., [http://smtcomp.sourceforge.net/2014/ SMT COMP 2014]
 
  
information on the web GUI (under construction) for presenting results [[Star_Exec_Presenter]]
+
To contact the steering committee of the termination competition, send an email to terminationcompetitionsc<at>lists.rwth-aachen.de.
  
Separate page with impressions from using the demo version of Star Exec, in 2012: [[Star_Exec_Test]]
+
The competition organizers can be reached at johannes.waldmann<at>htwk-leipzig.de

Latest revision as of 13:45, 11 October 2015

In 2014, the Termination Competition will be part of the FLoC Olympic Games.

Current News

Competition results at [1] . Demonstration results at [2]. Termination Competition 2014 Questionnaire. Also, check the mailing list [3]

Dates

  • call for tools, certifiers, problems: May 26
  • registration of tools: June 15
  • updates of registered tools, submission of problems: July 1
  • competition runs: July 19 - 21
  • results announced: July 21, during the Second FLoC Olympic Games Award Ceremony, Vienna.

Competition Categories and Awards

The competition contains several categories, grouped in three meta-categories:

  • termination of term rewriting (all categories with HO/FO-TRSs, with- or without strategies)
  • complexity analysis of term rewriting (all complexity categories)
  • termination of programming languages (Logic Programming, Haskell, Java, C, ...)

In each meta-category, a medal will be awarded to the highest-scoring solver.

For every meta-category, we consider the sum of the scores for each category within that meta-category: The score of a tool is determined by the number of other tools which could be beaten in that category.

This puts the emphasis on categories with many competitors. (In particular, a category with just one entrant would produce a zero score.) A category is only run at the competition if there are at least 2 participants and at least 40 examples for this category in the underlying termination problem data base.

New Categories

This year a new category on termination of C programs will be included (see the details here).

Other categories for "transition systems" or "large scale (Java) programs" are under consideration depending on the number of interested participants and available problems.

Competition Procedure

All participants in the same category will be run on a subset of the existing problems of this category. The number of problems used in the competition is not fixed and will depend on the number of existing problems. The problem selection algorithm will be the same as in previous years (link http://www.termination-portal.org/wiki/Termination_Competition_Problem_Selection_Algorithm), however because of moving to StarExec, there might be modifications of the rules suggested by the organizer and decided by the SC.

The wall-clock timeout will be 60 (up to 300) seconds, and 4 cores will be available (if a tool wants to use concurrent execution).

For nearly all categories, the tools will be started in their directory and obtain two parameters:

The tools are expected to give an answer (YES, NO, MAYBE) in the first line on stdout, followed by a proof in ASCII, HTML, or CPF format. Exceptions to these rules are the certified (see also the CPF-website) and complexity categories. See all existing categories for more details.

For those problems where a correct answer is (partially) known, any contradictory answer will be penalized with a high negative score. Moreover, those buggy systems may have the opportunity to provide a corrected version that will be run again after the end of the live execution (displaying the new results afterwards, but out of competition).

For those categories devoted to prove only termination or non-termination, the score of a tool is the number of non-contradictory answers minus the given penalization (if any).

Committees

Steering Committee

  • Jürgen Giesl, RWTH Aachen, Germany
  • Frederic Mesnard, Université de la Réunion, France
  • Albert Rubio (chair), UPC Barcelona, Spain
  • Rene Thiemann, Universität Innsbruck, Austria
  • Johannes Waldmann, HTWK Leipzig, Germany

Organizing Commmittee

  • Johannes Waldmann, HTWK Leipzig, Germany
  • Stefan von der Krone, HTWK Leipzig, Germany

Registration

Participants must register on StarExecRegistration, indicating the competition categories where they plan to enter tools and problems, and then upload their contributions to StarExec.

Note: if I (J. Waldmann) don't know you ("knowing" is roughly symmetrical), then I will ask you to specify: what termination tool you're working on, what competition categories you plan to take part in, your affiliation (in case you're a student, also the name of your advisor/research group leader). The email address you give in the registration should be your institutional one.

We recommend to register early. After the deadline, access to StarExec might be restricted. We need time to prepare the competition, and other competitions may be running in parallel.

It is highly recommended that participants also subscribe to the termtools mailing list, because that is where announcements will be made, and where discussion takes place.

Registration (Detail)

see this page: Termination Competition 2014 Registration

StarExec Wiki

Lots of useful information about StarExec is available here.

Technical Detail

We intend to run the competition on StarExec - a cross-community solver (tool) execution and benchmark (problem) library service under joint development (since 2012) at the University of Iowa and the University of Miami.

Technical details about the execution platform can be found here.

Contact

To contact the steering committee of the termination competition, send an email to terminationcompetitionsc<at>lists.rwth-aachen.de.

The competition organizers can be reached at johannes.waldmann<at>htwk-leipzig.de