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