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