TCM-July-2008 - Revision history

J.waldmann at 15:50, 16 July 2008

2008-07-16T15:50:19Z

C-Otto at 15:59, 15 July 2008

2008-07-15T15:59:52Z

C-Otto at 15:58, 15 July 2008

2008-07-15T15:58:30Z

C-Otto: To discuss

2008-07-15T15:54:42Z

To discuss

J.waldmann: New page: == Date/Time/Location == 15 July 2008, 6:30 pm, during RTA at Hagenberg == Agenda == * current status of the competition test run ** the "Torpa problem" (what can programs expect on $PA...

2008-07-15T13:01:18Z

New page: == Date/Time/Location == 15 July 2008, 6:30 pm, during RTA at Hagenberg == Agenda == * current status of the competition test run ** the "Torpa problem" (what can programs expect on $PA...

New page

== Date/Time/Location ==

15 July 2008, 6:30 pm, during RTA at Hagenberg

== Agenda ==

* current status of the competition test run
** the "Torpa problem" (what can programs expect on $PATH, $PWD)
** the "Jambox problem" (programs that write long proofs)
** Q: test run for certified termination?

* next steps
** submission of new prover versions
** submission of new problem (sets)
** test runs (by submitters)
** complete runs (by administrators)
** evaluation (by committee) (how and when)

* new category suggestions
** complexity analysis (Georg Moser, Johannes Waldmann)
** SN infinity (Hans Zantema, Jörg Endrullis)
** we have more categories than people?

* details for Termination Workshop 2009 Leipzig
** date? (needs to be decided soon, to book the venue)
** length/schedule? suggestion:
*** (day 1) sub-workshop on certified termination
*** (day 2, 3) termination workshop (if there are more submission, then already start on afternoon of day 1)
*** (day 4) would be possible to hold the IFIP WG 1.6 meeting
** program committee? suggestion: informal workshop, no refereeing, small committee, include people from communities of termination of logic programming, imperative programming

@@ Line 27: / Line 27: @@
 ** For CPU time limit the competition can run faster (if the tools run multithreaded), but there is no incentive to do so.
 ** My opinion: Because the machines have 16 CPU cores each, multithreading should be encouraged (read: wall time!)
 * details for Termination Workshop 2009 Leipzig

@@ Line 25: / Line 25: @@
 ** RAM usage (unlimited I guess)
 ** CPU usage (defined by wall time, so one may use 16 cores? CPU time, so 60 seconds singlethreaded translates to about 4 seconds with 16 threads?)
 * details for Termination Workshop 2009 Leipzig

@@ Line 3: / Line 3: @@
 July 2008, 6:30 pm, during RTA at Hagenberg
-== Agenda ==
+== Agenda/Minutes ==
 * current status of the competition test run
@@ Line 9: / Line 12: @@
 ** the "Jambox problem" (programs that write long proofs)
 ** Q: test run for certified termination?
 * next steps
 ** submission of new prover versions
 ** submission of new problem (sets)
 ** complete runs (by administrators)
 ** evaluation (by committee) (how and when)
 * new category suggestions
 ** complexity analysis (Georg Moser, Johannes Waldmann)
 ** SN infinity (Hans Zantema, Jörg Endrullis)
 ** we have more categories than people?
 * To discuss and clarify
@@ Line 28: / Line 57: @@
 ** My opinion: Because the machines have 16 CPU cores each, multithreading should be encouraged (read: wall time!)
 ** With wall time 60 seconds would be roughly equivalent to 960 seconds at the old competition
 * details for Termination Workshop 2009 Leipzig
@@ Line 36: / Line 69: @@
 *** (day 4) would be possible to hold the IFIP WG 1.6 meeting
 ** program committee? suggestion: informal workshop, no refereeing, small committee, include people from communities of termination of logic programming, imperative programming