MAYBE 726.08/297.02 MAYBE 726.08/297.02 726.08/297.02 We are left with following problem, upon which TcT provides the 726.08/297.02 certificate MAYBE. 726.08/297.02 726.08/297.02 Strict Trs: 726.08/297.02 { badd(x', Cons(x, xs)) -> badd(Cons(Nil(), Nil()), badd(x', xs)) 726.08/297.02 , badd(x, Nil()) -> x 726.08/297.02 , goal(x, y) -> badd(x, y) } 726.08/297.02 Obligation: 726.08/297.02 innermost runtime complexity 726.08/297.02 Answer: 726.08/297.02 MAYBE 726.08/297.02 726.08/297.02 None of the processors succeeded. 726.08/297.02 726.08/297.02 Details of failed attempt(s): 726.08/297.02 ----------------------------- 726.08/297.02 1) 'empty' failed due to the following reason: 726.08/297.02 726.08/297.02 Empty strict component of the problem is NOT empty. 726.08/297.02 726.08/297.02 2) 'Best' failed due to the following reason: 726.08/297.02 726.08/297.02 None of the processors succeeded. 726.08/297.02 726.08/297.02 Details of failed attempt(s): 726.08/297.02 ----------------------------- 726.08/297.02 1) 'With Problem ... (timeout of 297 seconds)' failed due to the 726.08/297.02 following reason: 726.08/297.02 726.08/297.02 Computation stopped due to timeout after 297.0 seconds. 726.08/297.02 726.08/297.02 2) 'Best' failed due to the following reason: 726.08/297.02 726.08/297.02 None of the processors succeeded. 726.08/297.02 726.08/297.02 Details of failed attempt(s): 726.08/297.02 ----------------------------- 726.08/297.02 1) 'Fastest (timeout of 24 seconds) (timeout of 297 seconds)' 726.08/297.02 failed due to the following reason: 726.08/297.02 726.08/297.02 Computation stopped due to timeout after 24.0 seconds. 726.08/297.02 726.08/297.02 2) 'With Problem ... (timeout of 148 seconds) (timeout of 297 726.08/297.02 seconds)' failed due to the following reason: 726.08/297.02 726.08/297.02 The weightgap principle applies (using the following nonconstant 726.08/297.02 growth matrix-interpretation) 726.08/297.02 726.08/297.02 The following argument positions are usable: 726.08/297.02 Uargs(badd) = {2} 726.08/297.02 726.08/297.02 TcT has computed the following matrix interpretation satisfying 726.08/297.02 not(EDA) and not(IDA(1)). 726.08/297.02 726.08/297.02 [badd](x1, x2) = [1] x1 + [1] x2 + [0] 726.08/297.02 726.08/297.02 [Cons](x1, x2) = [1] x1 + [1] x2 + [7] 726.08/297.02 726.08/297.02 [Nil] = [0] 726.08/297.02 726.08/297.02 [goal](x1, x2) = [1] x1 + [1] x2 + [7] 726.08/297.02 726.08/297.02 The order satisfies the following ordering constraints: 726.08/297.02 726.08/297.02 [badd(x', Cons(x, xs))] = [1] x' + [1] x + [1] xs + [7] 726.08/297.02 >= [1] x' + [1] xs + [7] 726.08/297.02 = [badd(Cons(Nil(), Nil()), badd(x', xs))] 726.08/297.02 726.08/297.02 [badd(x, Nil())] = [1] x + [0] 726.08/297.02 >= [1] x + [0] 726.08/297.02 = [x] 726.08/297.02 726.08/297.02 [goal(x, y)] = [1] x + [1] y + [7] 726.08/297.02 > [1] x + [1] y + [0] 726.08/297.02 = [badd(x, y)] 726.08/297.02 726.08/297.02 726.08/297.02 Further, it can be verified that all rules not oriented are covered by the weightgap condition. 726.08/297.02 726.08/297.02 We are left with following problem, upon which TcT provides the 726.08/297.02 certificate MAYBE. 726.08/297.02 726.08/297.02 Strict Trs: 726.08/297.02 { badd(x', Cons(x, xs)) -> badd(Cons(Nil(), Nil()), badd(x', xs)) 726.08/297.02 , badd(x, Nil()) -> x } 726.08/297.02 Weak Trs: { goal(x, y) -> badd(x, y) } 726.08/297.02 Obligation: 726.08/297.02 innermost runtime complexity 726.08/297.02 Answer: 726.08/297.02 MAYBE 726.08/297.02 726.08/297.02 The weightgap principle applies (using the following nonconstant 726.08/297.02 growth matrix-interpretation) 726.08/297.02 726.08/297.02 The following argument positions are usable: 726.08/297.02 Uargs(badd) = {2} 726.08/297.02 726.08/297.02 TcT has computed the following matrix interpretation satisfying 726.08/297.02 not(EDA) and not(IDA(1)). 726.08/297.02 726.08/297.02 [badd](x1, x2) = [1] x1 + [1] x2 + [0] 726.08/297.02 726.08/297.02 [Cons](x1, x2) = [1] x2 + [0] 726.08/297.02 726.08/297.02 [Nil] = [1] 726.08/297.02 726.08/297.02 [goal](x1, x2) = [1] x1 + [1] x2 + [7] 726.08/297.02 726.08/297.02 The order satisfies the following ordering constraints: 726.08/297.02 726.08/297.02 [badd(x', Cons(x, xs))] = [1] x' + [1] xs + [0] 726.08/297.02 ? [1] x' + [1] xs + [1] 726.08/297.02 = [badd(Cons(Nil(), Nil()), badd(x', xs))] 726.08/297.02 726.08/297.02 [badd(x, Nil())] = [1] x + [1] 726.08/297.02 > [1] x + [0] 726.08/297.02 = [x] 726.08/297.02 726.08/297.02 [goal(x, y)] = [1] x + [1] y + [7] 726.08/297.02 > [1] x + [1] y + [0] 726.08/297.02 = [badd(x, y)] 726.08/297.02 726.08/297.02 726.08/297.02 Further, it can be verified that all rules not oriented are covered by the weightgap condition. 726.08/297.02 726.08/297.02 We are left with following problem, upon which TcT provides the 726.08/297.02 certificate MAYBE. 726.08/297.02 726.08/297.02 Strict Trs: 726.08/297.02 { badd(x', Cons(x, xs)) -> badd(Cons(Nil(), Nil()), badd(x', xs)) } 726.08/297.02 Weak Trs: 726.08/297.02 { badd(x, Nil()) -> x 726.08/297.02 , goal(x, y) -> badd(x, y) } 726.08/297.02 Obligation: 726.08/297.02 innermost runtime complexity 726.08/297.02 Answer: 726.08/297.02 MAYBE 726.08/297.02 726.08/297.02 None of the processors succeeded. 726.08/297.02 726.08/297.02 Details of failed attempt(s): 726.08/297.02 ----------------------------- 726.08/297.02 1) 'empty' failed due to the following reason: 726.08/297.02 726.08/297.02 Empty strict component of the problem is NOT empty. 726.08/297.02 726.08/297.02 2) 'With Problem ...' failed due to the following reason: 726.08/297.02 726.08/297.02 None of the processors succeeded. 726.08/297.03 726.08/297.03 Details of failed attempt(s): 726.08/297.03 ----------------------------- 726.08/297.03 1) 'empty' failed due to the following reason: 726.08/297.03 726.08/297.03 Empty strict component of the problem is NOT empty. 726.08/297.03 726.08/297.03 2) 'Fastest' failed due to the following reason: 726.08/297.03 726.08/297.03 None of the processors succeeded. 726.08/297.03 726.08/297.03 Details of failed attempt(s): 726.08/297.03 ----------------------------- 726.08/297.03 1) 'With Problem ...' failed due to the following reason: 726.08/297.03 726.08/297.03 None of the processors succeeded. 726.08/297.03 726.08/297.03 Details of failed attempt(s): 726.08/297.03 ----------------------------- 726.08/297.03 1) 'empty' failed due to the following reason: 726.08/297.03 726.08/297.03 Empty strict component of the problem is NOT empty. 726.08/297.03 726.08/297.03 2) 'With Problem ...' failed due to the following reason: 726.08/297.03 726.08/297.03 None of the processors succeeded. 726.08/297.03 726.08/297.03 Details of failed attempt(s): 726.08/297.03 ----------------------------- 726.08/297.03 1) 'empty' failed due to the following reason: 726.08/297.03 726.08/297.03 Empty strict component of the problem is NOT empty. 726.08/297.03 726.08/297.03 2) 'With Problem ...' failed due to the following reason: 726.08/297.03 726.08/297.03 None of the processors succeeded. 726.08/297.03 726.08/297.03 Details of failed attempt(s): 726.08/297.03 ----------------------------- 726.08/297.03 1) 'empty' failed due to the following reason: 726.08/297.03 726.08/297.03 Empty strict component of the problem is NOT empty. 726.08/297.03 726.08/297.03 2) 'With Problem ...' failed due to the following reason: 726.08/297.03 726.08/297.03 Empty strict component of the problem is NOT empty. 726.08/297.03 726.08/297.03 726.08/297.03 726.08/297.03 726.08/297.03 2) 'With Problem ...' failed due to the following reason: 726.08/297.03 726.08/297.03 None of the processors succeeded. 726.08/297.03 726.08/297.03 Details of failed attempt(s): 726.08/297.03 ----------------------------- 726.08/297.03 1) 'empty' failed due to the following reason: 726.08/297.03 726.08/297.03 Empty strict component of the problem is NOT empty. 726.08/297.03 726.08/297.03 2) 'With Problem ...' failed due to the following reason: 726.08/297.03 726.08/297.03 Empty strict component of the problem is NOT empty. 726.08/297.03 726.08/297.03 726.08/297.03 726.08/297.03 726.08/297.03 726.08/297.03 3) 'Best' failed due to the following reason: 726.08/297.03 726.08/297.03 None of the processors succeeded. 726.08/297.03 726.08/297.03 Details of failed attempt(s): 726.08/297.03 ----------------------------- 726.08/297.03 1) 'Polynomial Path Order (PS) (timeout of 297 seconds)' failed due 726.08/297.03 to the following reason: 726.08/297.03 726.08/297.03 The input cannot be shown compatible 726.08/297.03 726.08/297.03 2) 'bsearch-popstar (timeout of 297 seconds)' failed due to the 726.08/297.03 following reason: 726.08/297.03 726.08/297.03 The input cannot be shown compatible 726.08/297.03 726.08/297.03 726.08/297.03 726.08/297.03 726.08/297.03 726.08/297.03 Arrrr.. 726.30/297.20 EOF