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