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