Termination Competition 2026 - Revision history

Ffrohn at 09:04, 9 July 2026

2026-07-09T09:04:03Z

Ffrohn at 10:01, 26 June 2026

2026-06-26T10:01:48Z

Ffrohn: /* Changes with respect to 2025 */

2026-06-25T13:43:26Z

Changes with respect to 2025

Ffrohn: /* Changes with respect to 2025 */

2026-06-25T13:42:18Z

Changes with respect to 2025

Ffrohn: /* Registration */

2026-06-23T08:08:26Z

Registration

Ffrohn: /* Changes with respect to 2025 */

2026-06-23T08:04:14Z

Changes with respect to 2025

Thiemann: change website of CPF

2026-06-17T08:04:04Z

change website of CPF

JCKassing: Update on the rules for the 2026 TermComp

2026-06-08T11:13:39Z

Update on the rules for the 2026 TermComp

Akihisa Yamada: /* Steering Committee */ affiliation

2026-05-29T02:48:19Z

Steering Committee: affiliation

Ffrohn at 07:40, 27 April 2026

2026-04-27T07:40:23Z

@@ Line 93: / Line 93: @@
 * Akihisa Yamada
 * Dieter Hofbauer, ASW Saarland
 == Changes with respect to 2025 ==

@@ Line 20: / Line 20: @@
 * Live Run: July 24/25
 * Presentation of the results at WST: July 25
 == Competition Categories ==

@@ Line 101: / Line 101: @@
 ** If one person submits several tools, or a tool that participates in more than one category, 5 benchmarks are still sufficient.
 ** The submitted examples can be for any non-demo category, not just the category (or categories) where the tool(s) of the submitter participates.
-** If your tool only participates in demo categories, then you don't need to submit secret benchmarks
+** If your tool only participates in demo categories, then you don't need to submit secret benchmarks.
 * Demo categories will only be run on request to the steering committee, and this request has to be justified somehow (e.g., by a paper, significant tool improvements, ...). The final decision is up to the SC.
 * Submissions to TPDB must have a README with a (short) description of the origin of the benchmarks.
 * We will do a full run and a live run, as described above.

@@ Line 93: / Line 93: @@
 Proposed changes:
-* In addition to the usual tracks, we will try to organize a '''knockout tournament'''.
+* <s>In addition to the usual tracks, we will try to organize a '''knockout tournament'''.</s>
 Adopted changes:
@@ Line 100: / Line 100: @@
 * Every participant has to submit at least 5 and at most 20 new '''secret''' benchmarks.
 ** If one person submits several tools, or a tool that participates in more than one category, 5 benchmarks are still sufficient.
-** The submitted examples can be for any category, not just the category (or categories) where the tool(s) of the submitter participates.
+** The submitted examples can be for any non-demo category, not just the category (or categories) where the tool(s) of the submitter participates.
 * Demo categories will only be run on request to the steering committee, and this request has to be justified somehow (e.g., by a paper, significant tool improvements, ...). The final decision is up to the SC.
 * Submissions to TPDB must have a README with a (short) description of the origin of the benchmarks.
 * We will do a full run and a live run, as described above.

@@ Line 52: / Line 52: @@
 To submit a tool, please follow the instruction at [https://github.com/TermCOMP/registration this repository].
-Every participant must submit at least five new '''secret''' benchmarks via email to florian.frohn@cs.rwth-aachen.de (unless the size of the benchmarks exceeds 5MB -- in that case, please get in touch to figure out another way).
+Every participant must submit between 5 and 20 new '''secret''' benchmarks via email to florian.frohn@cs.rwth-aachen.de (unless the size of the benchmarks exceeds 5MB -- in that case, please get in touch to figure out another way).
 Please also include a README with a (short) description of the origin of the benchmarks.
 After the competition, these benchmarks will become part of TPDB.

@@ Line 42: / Line 42: @@
 Further technical information is available [[Termination Competition 2026 technical details|here]].
-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.
+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 [https://isafor-ceta.uibk.ac.at/cpf3.html 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 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).

@@ Line 15: / Line 15: @@
 == Dates  ==
 * Tool and Benchmark Submission: June 26
 * Full Run: July 13-17
@@ Line 22: / Line 23: @@
 == Competition Categories ==
-The competition contains several categories for termination and complexity from the areas of term rewriting (all categories with HO/FO-TRSs, with- or without strategies) and programming languages (Logic Programming, Haskell, Java, C, integer transition systems, ...)
+The competition contains several categories for termination and complexity from the areas of term rewriting (all categories with HO/FO-TRSs, with- or without strategies) and programming languages (Logic Programming, Haskell, Java, C, integer transition systems, ...), see [[Termination Competition]] for more details on all the categories.
-Proposals for new categories are welcome.
+Proposals for new categories are welcome!
 A category is only run at the competition if there are at least 2 participants, at least 40 examples
-for this category in the underlying termination problem data base, and clearly defined rules.
+for this category in the underlying termination problem data base, and clearly defined rules in the [https://github.com/TermCOMP/termcomp-reference termination competition reference].
 == Competition Procedure ==
@@ Line 47: / Line 48: @@
 A proof or answer that is known to be wrong will be penalized by -10 points, if it remains after the bugfix deadline.
 The SC will decide what should be penalized, depending on the discussion among the participants.
 == Registration ==
@@ Line 82: / Line 74: @@
 To contact the steering committee, send an email to terminationcompetitionsc<at>lists.rwth-aachen.de.
 == Changes with respect to 2025 ==
@@ Line 95: / Line 96: @@
 Adopted changes:
-* We will only run categories with clearly defined rules.
+* We will only run categories with clearly defined rules in the [https://github.com/TermCOMP/termcomp-reference termination competition reference].
 * Every participant has to submit at least five new '''secret''' benchmarks
-* Demo categories will only be run on request, and this request has to be justified somehow (e.g., by a paper, significant tool improvements, ...). The final decision is up to the SC.
+* Demo categories will only be run on request to the steering committee, and this request has to be justified somehow (e.g., by a paper, significant tool improvements, ...). The final decision is up to the SC.
 * Submissions to TPDB must have a README with a (short) description of the origin of the benchmarks.
 * We will do a full run and a live run, as described above.

@@ Line 54: / Line 54: @@
 * Georg Moser, University of Innsbruck
 * Étienne Payet, Université de La Réunion
-* Akihisa Yamada, AIST Tokyo Waterfront
+* Akihisa Yamada
 * Dieter Hofbauer, ASW Saarland

@@ Line 75: / Line 75: @@
 (a successor of [https://github.com/stefanvonderkrone/star-exec-presenter star-exec-presenter] developed at HTWK Leipzig).
 Technical details about the execution platform are available [[Termination Competition 2026 technical details|here]].
 == Contact ==