MAYBE 651.80/297.02 MAYBE 651.80/297.02 651.80/297.02 We are left with following problem, upon which TcT provides the 651.80/297.02 certificate MAYBE. 651.80/297.02 651.80/297.02 Strict Trs: { a(b(x)) -> b(b(a(a(x)))) } 651.80/297.02 Obligation: 651.80/297.02 runtime complexity 651.80/297.02 Answer: 651.80/297.02 MAYBE 651.80/297.02 651.80/297.02 The input is overlay and right-linear. Switching to innermost 651.80/297.02 rewriting. 651.80/297.02 651.80/297.02 We are left with following problem, upon which TcT provides the 651.80/297.02 certificate MAYBE. 651.80/297.02 651.80/297.02 Strict Trs: { a(b(x)) -> b(b(a(a(x)))) } 651.80/297.02 Obligation: 651.80/297.02 innermost runtime complexity 651.80/297.02 Answer: 651.80/297.02 MAYBE 651.80/297.02 651.80/297.02 None of the processors succeeded. 651.80/297.02 651.80/297.02 Details of failed attempt(s): 651.80/297.02 ----------------------------- 651.80/297.02 1) 'empty' failed due to the following reason: 651.80/297.02 651.80/297.02 Empty strict component of the problem is NOT empty. 651.80/297.02 651.80/297.02 2) 'Best' failed due to the following reason: 651.80/297.02 651.80/297.02 None of the processors succeeded. 651.80/297.02 651.80/297.02 Details of failed attempt(s): 651.80/297.02 ----------------------------- 651.80/297.02 1) 'With Problem ... (timeout of 297 seconds)' failed due to the 651.80/297.02 following reason: 651.80/297.02 651.80/297.02 Computation stopped due to timeout after 297.0 seconds. 651.80/297.02 651.80/297.02 2) 'Best' failed due to the following reason: 651.80/297.02 651.80/297.02 None of the processors succeeded. 651.80/297.02 651.80/297.02 Details of failed attempt(s): 651.80/297.02 ----------------------------- 651.80/297.02 1) 'With Problem ... (timeout of 148 seconds) (timeout of 297 651.80/297.02 seconds)' failed due to the following reason: 651.80/297.02 651.80/297.02 None of the processors succeeded. 651.80/297.02 651.80/297.02 Details of failed attempt(s): 651.80/297.02 ----------------------------- 651.80/297.02 1) 'empty' failed due to the following reason: 651.80/297.02 651.80/297.02 Empty strict component of the problem is NOT empty. 651.80/297.02 651.80/297.02 2) 'With Problem ...' failed due to the following reason: 651.80/297.02 651.80/297.02 None of the processors succeeded. 651.80/297.02 651.80/297.02 Details of failed attempt(s): 651.80/297.02 ----------------------------- 651.80/297.02 1) 'empty' failed due to the following reason: 651.80/297.02 651.80/297.02 Empty strict component of the problem is NOT empty. 651.80/297.02 651.80/297.02 2) 'Fastest' failed due to the following reason: 651.80/297.02 651.80/297.02 None of the processors succeeded. 651.80/297.02 651.80/297.02 Details of failed attempt(s): 651.80/297.02 ----------------------------- 651.80/297.02 1) 'With Problem ...' failed due to the following reason: 651.80/297.02 651.80/297.02 None of the processors succeeded. 651.80/297.02 651.80/297.02 Details of failed attempt(s): 651.80/297.02 ----------------------------- 651.80/297.02 1) 'empty' failed due to the following reason: 651.80/297.02 651.80/297.02 Empty strict component of the problem is NOT empty. 651.80/297.02 651.80/297.02 2) 'With Problem ...' failed due to the following reason: 651.80/297.02 651.80/297.02 None of the processors succeeded. 651.80/297.02 651.80/297.02 Details of failed attempt(s): 651.80/297.02 ----------------------------- 651.80/297.02 1) 'empty' failed due to the following reason: 651.80/297.02 651.80/297.02 Empty strict component of the problem is NOT empty. 651.80/297.02 651.80/297.02 2) 'With Problem ...' failed due to the following reason: 651.80/297.02 651.80/297.02 None of the processors succeeded. 651.80/297.02 651.80/297.02 Details of failed attempt(s): 651.80/297.02 ----------------------------- 651.80/297.02 1) 'empty' failed due to the following reason: 651.80/297.02 651.80/297.02 Empty strict component of the problem is NOT empty. 651.80/297.02 651.80/297.02 2) 'With Problem ...' failed due to the following reason: 651.80/297.02 651.80/297.02 Empty strict component of the problem is NOT empty. 651.80/297.02 651.80/297.02 651.80/297.02 651.80/297.02 651.80/297.02 2) 'With Problem ...' failed due to the following reason: 651.80/297.02 651.80/297.02 None of the processors succeeded. 651.80/297.02 651.80/297.02 Details of failed attempt(s): 651.80/297.02 ----------------------------- 651.80/297.02 1) 'empty' failed due to the following reason: 651.80/297.02 651.80/297.02 Empty strict component of the problem is NOT empty. 651.80/297.02 651.80/297.02 2) 'With Problem ...' failed due to the following reason: 651.80/297.02 651.80/297.02 Empty strict component of the problem is NOT empty. 651.80/297.02 651.80/297.02 651.80/297.02 651.80/297.02 651.80/297.02 651.80/297.02 2) 'Fastest (timeout of 24 seconds) (timeout of 297 seconds)' 651.80/297.02 failed due to the following reason: 651.80/297.02 651.80/297.02 Computation stopped due to timeout after 24.0 seconds. 651.80/297.02 651.80/297.02 3) 'Best' failed due to the following reason: 651.80/297.02 651.80/297.02 None of the processors succeeded. 651.80/297.02 651.80/297.02 Details of failed attempt(s): 651.80/297.02 ----------------------------- 651.80/297.02 1) 'Polynomial Path Order (PS) (timeout of 297 seconds)' failed due 651.80/297.02 to the following reason: 651.80/297.02 651.80/297.02 The input cannot be shown compatible 651.80/297.02 651.80/297.02 2) 'bsearch-popstar (timeout of 297 seconds)' failed due to the 651.80/297.02 following reason: 651.80/297.02 651.80/297.02 The input cannot be shown compatible 651.80/297.02 651.80/297.02 651.80/297.02 651.80/297.02 651.80/297.02 651.80/297.02 Arrrr.. 651.93/297.16 EOF