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