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