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