MAYBE 978.85/297.07 MAYBE 978.85/297.07 978.85/297.07 We are left with following problem, upon which TcT provides the 978.85/297.07 certificate MAYBE. 978.85/297.07 978.85/297.07 Strict Trs: 978.85/297.07 { ack(0(), y) -> s(y) 978.85/297.07 , ack(s(x), y) -> f(x, x) 978.85/297.07 , ack(s(x), 0()) -> ack(x, s(0())) 978.85/297.07 , ack(s(x), s(y)) -> ack(x, ack(s(x), y)) 978.85/297.07 , f(x, y) -> ack(x, y) 978.85/297.07 , f(x, s(y)) -> f(y, x) 978.85/297.07 , f(s(x), y) -> f(x, s(x)) } 978.85/297.07 Obligation: 978.85/297.07 runtime complexity 978.85/297.07 Answer: 978.85/297.07 MAYBE 978.85/297.07 978.85/297.07 None of the processors succeeded. 978.85/297.07 978.85/297.07 Details of failed attempt(s): 978.85/297.07 ----------------------------- 978.85/297.07 1) 'With Problem ... (timeout of 297 seconds)' failed due to the 978.85/297.07 following reason: 978.85/297.07 978.85/297.07 Computation stopped due to timeout after 297.0 seconds. 978.85/297.07 978.85/297.07 2) 'Best' failed due to the following reason: 978.85/297.07 978.85/297.07 None of the processors succeeded. 978.85/297.07 978.85/297.07 Details of failed attempt(s): 978.85/297.07 ----------------------------- 978.85/297.07 1) 'With Problem ... (timeout of 148 seconds) (timeout of 297 978.85/297.07 seconds)' failed due to the following reason: 978.85/297.07 978.85/297.07 None of the processors succeeded. 978.85/297.07 978.85/297.07 Details of failed attempt(s): 978.85/297.07 ----------------------------- 978.85/297.07 1) 'empty' failed due to the following reason: 978.85/297.07 978.85/297.07 Empty strict component of the problem is NOT empty. 978.85/297.07 978.85/297.07 2) 'With Problem ...' failed due to the following reason: 978.85/297.07 978.85/297.07 None of the processors succeeded. 978.85/297.07 978.85/297.07 Details of failed attempt(s): 978.85/297.07 ----------------------------- 978.85/297.07 1) 'empty' failed due to the following reason: 978.85/297.07 978.85/297.07 Empty strict component of the problem is NOT empty. 978.85/297.07 978.85/297.07 2) 'Fastest' failed due to the following reason: 978.85/297.07 978.85/297.07 None of the processors succeeded. 978.85/297.07 978.85/297.07 Details of failed attempt(s): 978.85/297.07 ----------------------------- 978.85/297.07 1) 'With Problem ...' failed due to the following reason: 978.85/297.07 978.85/297.07 None of the processors succeeded. 978.85/297.07 978.85/297.07 Details of failed attempt(s): 978.85/297.07 ----------------------------- 978.85/297.07 1) 'empty' failed due to the following reason: 978.85/297.07 978.85/297.07 Empty strict component of the problem is NOT empty. 978.85/297.07 978.85/297.07 2) 'With Problem ...' failed due to the following reason: 978.85/297.07 978.85/297.07 Empty strict component of the problem is NOT empty. 978.85/297.07 978.85/297.07 978.85/297.07 2) 'With Problem ...' failed due to the following reason: 978.85/297.07 978.85/297.07 None of the processors succeeded. 978.85/297.07 978.85/297.07 Details of failed attempt(s): 978.85/297.07 ----------------------------- 978.85/297.07 1) 'empty' failed due to the following reason: 978.85/297.07 978.85/297.07 Empty strict component of the problem is NOT empty. 978.85/297.07 978.85/297.07 2) 'With Problem ...' failed due to the following reason: 978.85/297.07 978.85/297.07 None of the processors succeeded. 978.85/297.07 978.85/297.07 Details of failed attempt(s): 978.85/297.07 ----------------------------- 978.85/297.07 1) 'empty' failed due to the following reason: 978.85/297.07 978.85/297.07 Empty strict component of the problem is NOT empty. 978.85/297.07 978.85/297.07 2) 'With Problem ...' failed due to the following reason: 978.85/297.07 978.85/297.07 None of the processors succeeded. 978.85/297.07 978.85/297.07 Details of failed attempt(s): 978.85/297.07 ----------------------------- 978.85/297.07 1) 'empty' failed due to the following reason: 978.85/297.07 978.85/297.07 Empty strict component of the problem is NOT empty. 978.85/297.07 978.85/297.07 2) 'With Problem ...' failed due to the following reason: 978.85/297.07 978.85/297.07 Empty strict component of the problem is NOT empty. 978.85/297.07 978.85/297.07 978.85/297.07 978.85/297.07 978.85/297.07 978.85/297.07 978.85/297.07 978.85/297.07 2) 'Best' failed due to the following reason: 978.85/297.07 978.85/297.07 None of the processors succeeded. 978.85/297.07 978.85/297.07 Details of failed attempt(s): 978.85/297.07 ----------------------------- 978.85/297.07 1) 'Polynomial Path Order (PS) (timeout of 297 seconds)' failed due 978.85/297.07 to the following reason: 978.85/297.07 978.85/297.07 The processor is inapplicable, reason: 978.85/297.07 Processor only applicable for innermost runtime complexity analysis 978.85/297.07 978.85/297.07 2) 'bsearch-popstar (timeout of 297 seconds)' failed due to the 978.85/297.07 following reason: 978.85/297.07 978.85/297.07 The processor is inapplicable, reason: 978.85/297.07 Processor only applicable for innermost runtime complexity analysis 978.85/297.07 978.85/297.07 978.85/297.07 3) 'Fastest (timeout of 24 seconds) (timeout of 297 seconds)' 978.85/297.07 failed due to the following reason: 978.85/297.07 978.85/297.07 None of the processors succeeded. 978.85/297.07 978.85/297.07 Details of failed attempt(s): 978.85/297.07 ----------------------------- 978.85/297.07 1) 'Bounds with minimal-enrichment and initial automaton 'match'' 978.85/297.07 failed due to the following reason: 978.85/297.07 978.85/297.07 match-boundness of the problem could not be verified. 978.85/297.07 978.85/297.07 2) 'Bounds with perSymbol-enrichment and initial automaton 'match'' 978.85/297.07 failed due to the following reason: 978.85/297.07 978.85/297.07 match-boundness of the problem could not be verified. 978.85/297.07 978.85/297.07 978.85/297.07 978.85/297.07 3) 'Weak Dependency Pairs (timeout of 297 seconds)' failed due to 978.85/297.07 the following reason: 978.85/297.07 978.85/297.07 We add the following weak dependency pairs: 978.85/297.07 978.85/297.07 Strict DPs: 978.85/297.07 { ack^#(0(), y) -> c_1(y) 978.85/297.07 , ack^#(s(x), y) -> c_2(f^#(x, x)) 978.85/297.07 , ack^#(s(x), 0()) -> c_3(ack^#(x, s(0()))) 978.85/297.07 , ack^#(s(x), s(y)) -> c_4(ack^#(x, ack(s(x), y))) 978.85/297.07 , f^#(x, y) -> c_5(ack^#(x, y)) 978.85/297.07 , f^#(x, s(y)) -> c_6(f^#(y, x)) 978.85/297.07 , f^#(s(x), y) -> c_7(f^#(x, s(x))) } 978.85/297.07 978.85/297.07 and mark the set of starting terms. 978.85/297.07 978.85/297.07 We are left with following problem, upon which TcT provides the 978.85/297.07 certificate MAYBE. 978.85/297.07 978.85/297.07 Strict DPs: 978.85/297.07 { ack^#(0(), y) -> c_1(y) 978.85/297.07 , ack^#(s(x), y) -> c_2(f^#(x, x)) 978.85/297.07 , ack^#(s(x), 0()) -> c_3(ack^#(x, s(0()))) 978.85/297.07 , ack^#(s(x), s(y)) -> c_4(ack^#(x, ack(s(x), y))) 978.85/297.07 , f^#(x, y) -> c_5(ack^#(x, y)) 978.85/297.07 , f^#(x, s(y)) -> c_6(f^#(y, x)) 978.85/297.07 , f^#(s(x), y) -> c_7(f^#(x, s(x))) } 978.85/297.07 Strict Trs: 978.85/297.07 { ack(0(), y) -> s(y) 978.85/297.07 , ack(s(x), y) -> f(x, x) 978.85/297.07 , ack(s(x), 0()) -> ack(x, s(0())) 978.85/297.07 , ack(s(x), s(y)) -> ack(x, ack(s(x), y)) 978.85/297.07 , f(x, y) -> ack(x, y) 978.85/297.07 , f(x, s(y)) -> f(y, x) 978.85/297.07 , f(s(x), y) -> f(x, s(x)) } 978.85/297.07 Obligation: 978.85/297.07 runtime complexity 978.85/297.07 Answer: 978.85/297.07 MAYBE 978.85/297.07 978.85/297.07 Empty strict component of the problem is NOT empty. 978.85/297.07 978.85/297.07 978.85/297.07 Arrrr.. 980.03/298.07 EOF