MAYBE 708.40/297.12 MAYBE 708.40/297.12 708.40/297.12 We are left with following problem, upon which TcT provides the 708.40/297.12 certificate MAYBE. 708.40/297.12 708.40/297.12 Strict Trs: 708.40/297.12 { gt(0(), y) -> false() 708.40/297.12 , gt(s(x), 0()) -> true() 708.40/297.12 , gt(s(x), s(y)) -> gt(x, y) 708.40/297.12 , plus(0(), y) -> y 708.40/297.12 , plus(s(x), y) -> s(plus(x, y)) 708.40/297.12 , double(0()) -> 0() 708.40/297.12 , double(s(x)) -> s(s(double(x))) 708.40/297.12 , average(x, y) -> aver(plus(x, y), 0()) 708.40/297.12 , aver(sum, z) -> if(gt(sum, double(z)), sum, z) 708.40/297.12 , if(false(), sum, z) -> z 708.40/297.12 , if(true(), sum, z) -> aver(sum, s(z)) } 708.40/297.12 Obligation: 708.40/297.12 innermost runtime complexity 708.40/297.12 Answer: 708.40/297.12 MAYBE 708.40/297.12 708.40/297.12 None of the processors succeeded. 708.40/297.12 708.40/297.12 Details of failed attempt(s): 708.40/297.12 ----------------------------- 708.40/297.12 1) 'empty' failed due to the following reason: 708.40/297.12 708.40/297.12 Empty strict component of the problem is NOT empty. 708.40/297.12 708.40/297.12 2) 'Best' failed due to the following reason: 708.40/297.12 708.40/297.12 None of the processors succeeded. 708.40/297.12 708.40/297.12 Details of failed attempt(s): 708.40/297.12 ----------------------------- 708.40/297.12 1) 'With Problem ... (timeout of 297 seconds)' failed due to the 708.40/297.12 following reason: 708.40/297.12 708.40/297.12 Computation stopped due to timeout after 297.0 seconds. 708.40/297.12 708.40/297.12 2) 'Best' failed due to the following reason: 708.40/297.12 708.40/297.12 None of the processors succeeded. 708.40/297.12 708.40/297.12 Details of failed attempt(s): 708.40/297.12 ----------------------------- 708.40/297.12 1) 'With Problem ... (timeout of 148 seconds) (timeout of 297 708.40/297.12 seconds)' failed due to the following reason: 708.40/297.12 708.40/297.12 Computation stopped due to timeout after 148.0 seconds. 708.40/297.12 708.40/297.12 2) 'Best' failed due to the following reason: 708.40/297.12 708.40/297.12 None of the processors succeeded. 708.40/297.12 708.40/297.12 Details of failed attempt(s): 708.40/297.12 ----------------------------- 708.40/297.12 1) 'bsearch-popstar (timeout of 297 seconds)' failed due to the 708.40/297.12 following reason: 708.40/297.12 708.40/297.12 The input cannot be shown compatible 708.40/297.12 708.40/297.12 2) 'Polynomial Path Order (PS) (timeout of 297 seconds)' failed due 708.40/297.12 to the following reason: 708.40/297.12 708.40/297.12 The input cannot be shown compatible 708.40/297.12 708.40/297.12 708.40/297.12 3) 'Fastest (timeout of 24 seconds) (timeout of 297 seconds)' 708.40/297.12 failed due to the following reason: 708.40/297.12 708.40/297.12 None of the processors succeeded. 708.40/297.12 708.40/297.12 Details of failed attempt(s): 708.40/297.12 ----------------------------- 708.40/297.12 1) 'Bounds with minimal-enrichment and initial automaton 'match'' 708.40/297.12 failed due to the following reason: 708.40/297.12 708.40/297.12 match-boundness of the problem could not be verified. 708.40/297.12 708.40/297.12 2) 'Bounds with perSymbol-enrichment and initial automaton 'match'' 708.40/297.12 failed due to the following reason: 708.40/297.12 708.40/297.12 match-boundness of the problem could not be verified. 708.40/297.12 708.40/297.12 708.40/297.12 708.40/297.12 708.40/297.12 708.40/297.12 Arrrr.. 708.40/297.17 EOF