MAYBE 820.13/297.02 MAYBE 820.13/297.02 820.13/297.02 We are left with following problem, upon which TcT provides the 820.13/297.02 certificate MAYBE. 820.13/297.02 820.13/297.02 Strict Trs: 820.13/297.02 { *(x, +(y, f(z))) -> *(g(x, z), +(y, y)) 820.13/297.02 , *(*(x, y), z) -> *(x, *(y, z)) 820.13/297.02 , *(+(x, y), z) -> +(*(x, z), *(y, z)) } 820.13/297.02 Obligation: 820.13/297.02 innermost runtime complexity 820.13/297.02 Answer: 820.13/297.02 MAYBE 820.13/297.02 820.13/297.02 None of the processors succeeded. 820.13/297.02 820.13/297.02 Details of failed attempt(s): 820.13/297.02 ----------------------------- 820.13/297.02 1) 'empty' failed due to the following reason: 820.13/297.02 820.13/297.02 Empty strict component of the problem is NOT empty. 820.13/297.02 820.13/297.02 2) 'Best' failed due to the following reason: 820.13/297.02 820.13/297.02 None of the processors succeeded. 820.13/297.02 820.13/297.02 Details of failed attempt(s): 820.13/297.02 ----------------------------- 820.13/297.02 1) 'With Problem ... (timeout of 297 seconds)' failed due to the 820.13/297.02 following reason: 820.13/297.02 820.13/297.02 Computation stopped due to timeout after 297.0 seconds. 820.13/297.02 820.13/297.02 2) 'Best' failed due to the following reason: 820.13/297.02 820.13/297.02 None of the processors succeeded. 820.13/297.02 820.13/297.02 Details of failed attempt(s): 820.13/297.02 ----------------------------- 820.13/297.02 1) 'With Problem ... (timeout of 148 seconds) (timeout of 297 820.13/297.02 seconds)' failed due to the following reason: 820.13/297.02 820.13/297.02 None of the processors succeeded. 820.13/297.02 820.13/297.02 Details of failed attempt(s): 820.13/297.02 ----------------------------- 820.13/297.02 1) 'empty' failed due to the following reason: 820.13/297.02 820.13/297.02 Empty strict component of the problem is NOT empty. 820.13/297.02 820.13/297.02 2) 'With Problem ...' failed due to the following reason: 820.13/297.02 820.13/297.02 None of the processors succeeded. 820.13/297.02 820.13/297.02 Details of failed attempt(s): 820.13/297.02 ----------------------------- 820.13/297.02 1) 'empty' failed due to the following reason: 820.13/297.02 820.13/297.02 Empty strict component of the problem is NOT empty. 820.13/297.02 820.13/297.02 2) 'Fastest' failed due to the following reason: 820.13/297.02 820.13/297.02 None of the processors succeeded. 820.13/297.02 820.13/297.02 Details of failed attempt(s): 820.13/297.02 ----------------------------- 820.13/297.02 1) 'With Problem ...' failed due to the following reason: 820.13/297.02 820.13/297.02 None of the processors succeeded. 820.13/297.02 820.13/297.02 Details of failed attempt(s): 820.13/297.02 ----------------------------- 820.13/297.02 1) 'empty' failed due to the following reason: 820.13/297.02 820.13/297.02 Empty strict component of the problem is NOT empty. 820.13/297.02 820.13/297.02 2) 'With Problem ...' failed due to the following reason: 820.13/297.02 820.13/297.02 None of the processors succeeded. 820.13/297.02 820.13/297.02 Details of failed attempt(s): 820.13/297.02 ----------------------------- 820.13/297.02 1) 'empty' failed due to the following reason: 820.13/297.02 820.13/297.02 Empty strict component of the problem is NOT empty. 820.13/297.02 820.13/297.02 2) 'With Problem ...' failed due to the following reason: 820.13/297.02 820.13/297.02 None of the processors succeeded. 820.13/297.02 820.13/297.02 Details of failed attempt(s): 820.13/297.02 ----------------------------- 820.13/297.02 1) 'empty' failed due to the following reason: 820.13/297.02 820.13/297.02 Empty strict component of the problem is NOT empty. 820.13/297.02 820.13/297.02 2) 'With Problem ...' failed due to the following reason: 820.13/297.02 820.13/297.02 Empty strict component of the problem is NOT empty. 820.13/297.02 820.13/297.02 820.13/297.02 820.13/297.02 820.13/297.02 2) 'With Problem ...' failed due to the following reason: 820.13/297.02 820.13/297.02 None of the processors succeeded. 820.13/297.02 820.13/297.02 Details of failed attempt(s): 820.13/297.02 ----------------------------- 820.13/297.02 1) 'empty' failed due to the following reason: 820.13/297.02 820.13/297.02 Empty strict component of the problem is NOT empty. 820.13/297.02 820.13/297.02 2) 'With Problem ...' failed due to the following reason: 820.13/297.02 820.13/297.02 Empty strict component of the problem is NOT empty. 820.13/297.02 820.13/297.02 820.13/297.02 820.13/297.02 820.13/297.02 820.13/297.02 2) 'Best' failed due to the following reason: 820.13/297.02 820.13/297.02 None of the processors succeeded. 820.13/297.02 820.13/297.02 Details of failed attempt(s): 820.13/297.02 ----------------------------- 820.13/297.02 1) 'Polynomial Path Order (PS) (timeout of 297 seconds)' failed due 820.13/297.02 to the following reason: 820.13/297.02 820.13/297.02 The input cannot be shown compatible 820.13/297.02 820.13/297.02 2) 'bsearch-popstar (timeout of 297 seconds)' failed due to the 820.13/297.02 following reason: 820.13/297.02 820.13/297.02 The input cannot be shown compatible 820.13/297.02 820.13/297.02 820.13/297.02 3) 'Fastest (timeout of 24 seconds) (timeout of 297 seconds)' 820.13/297.02 failed due to the following reason: 820.13/297.02 820.13/297.02 None of the processors succeeded. 820.13/297.02 820.13/297.02 Details of failed attempt(s): 820.13/297.02 ----------------------------- 820.13/297.02 1) 'Bounds with minimal-enrichment and initial automaton 'match'' 820.13/297.02 failed due to the following reason: 820.13/297.02 820.13/297.02 match-boundness of the problem could not be verified. 820.13/297.02 820.13/297.02 2) 'Bounds with perSymbol-enrichment and initial automaton 'match'' 820.13/297.02 failed due to the following reason: 820.13/297.02 820.13/297.02 match-boundness of the problem could not be verified. 820.13/297.02 820.13/297.02 820.13/297.02 820.13/297.02 820.13/297.02 820.13/297.02 Arrrr.. 820.56/297.48 EOF