MAYBE 905.76/297.03 MAYBE 905.76/297.03 905.76/297.03 We are left with following problem, upon which TcT provides the 905.76/297.03 certificate MAYBE. 905.76/297.03 905.76/297.03 Strict Trs: 905.76/297.03 { *(x, +(y, f(z))) -> *(g(x, z), +(y, y)) 905.76/297.03 , *(*(x, y), z) -> *(x, *(y, z)) 905.76/297.03 , *(+(x, y), z) -> +(*(x, z), *(y, z)) } 905.76/297.03 Obligation: 905.76/297.03 runtime complexity 905.76/297.03 Answer: 905.76/297.03 MAYBE 905.76/297.03 905.76/297.03 None of the processors succeeded. 905.76/297.03 905.76/297.03 Details of failed attempt(s): 905.76/297.03 ----------------------------- 905.76/297.03 1) 'With Problem ... (timeout of 297 seconds)' failed due to the 905.76/297.03 following reason: 905.76/297.03 905.76/297.03 Computation stopped due to timeout after 297.0 seconds. 905.76/297.03 905.76/297.03 2) 'Best' failed due to the following reason: 905.76/297.03 905.76/297.03 None of the processors succeeded. 905.76/297.03 905.76/297.03 Details of failed attempt(s): 905.76/297.03 ----------------------------- 905.76/297.03 1) 'With Problem ... (timeout of 148 seconds) (timeout of 297 905.76/297.03 seconds)' failed due to the following reason: 905.76/297.03 905.76/297.03 None of the processors succeeded. 905.76/297.03 905.76/297.03 Details of failed attempt(s): 905.76/297.03 ----------------------------- 905.76/297.03 1) 'empty' failed due to the following reason: 905.76/297.03 905.76/297.03 Empty strict component of the problem is NOT empty. 905.76/297.03 905.76/297.03 2) 'With Problem ...' failed due to the following reason: 905.76/297.03 905.76/297.03 None of the processors succeeded. 905.76/297.03 905.76/297.03 Details of failed attempt(s): 905.76/297.03 ----------------------------- 905.76/297.03 1) 'empty' failed due to the following reason: 905.76/297.03 905.76/297.03 Empty strict component of the problem is NOT empty. 905.76/297.03 905.76/297.03 2) 'Fastest' failed due to the following reason: 905.76/297.03 905.76/297.03 None of the processors succeeded. 905.76/297.03 905.76/297.03 Details of failed attempt(s): 905.76/297.03 ----------------------------- 905.76/297.03 1) 'With Problem ...' failed due to the following reason: 905.76/297.03 905.76/297.03 None of the processors succeeded. 905.76/297.03 905.76/297.03 Details of failed attempt(s): 905.76/297.03 ----------------------------- 905.76/297.03 1) 'empty' failed due to the following reason: 905.76/297.03 905.76/297.03 Empty strict component of the problem is NOT empty. 905.76/297.03 905.76/297.03 2) 'With Problem ...' failed due to the following reason: 905.76/297.03 905.76/297.03 None of the processors succeeded. 905.76/297.03 905.76/297.03 Details of failed attempt(s): 905.76/297.03 ----------------------------- 905.76/297.03 1) 'empty' failed due to the following reason: 905.76/297.03 905.76/297.03 Empty strict component of the problem is NOT empty. 905.76/297.03 905.76/297.03 2) 'With Problem ...' failed due to the following reason: 905.76/297.03 905.76/297.03 None of the processors succeeded. 905.76/297.03 905.76/297.03 Details of failed attempt(s): 905.76/297.03 ----------------------------- 905.76/297.03 1) 'empty' failed due to the following reason: 905.76/297.03 905.76/297.03 Empty strict component of the problem is NOT empty. 905.76/297.03 905.76/297.03 2) 'With Problem ...' failed due to the following reason: 905.76/297.03 905.76/297.03 Empty strict component of the problem is NOT empty. 905.76/297.03 905.76/297.03 905.76/297.03 905.76/297.03 905.76/297.03 2) 'With Problem ...' failed due to the following reason: 905.76/297.03 905.76/297.03 None of the processors succeeded. 905.76/297.03 905.76/297.03 Details of failed attempt(s): 905.76/297.03 ----------------------------- 905.76/297.03 1) 'empty' failed due to the following reason: 905.76/297.03 905.76/297.03 Empty strict component of the problem is NOT empty. 905.76/297.03 905.76/297.03 2) 'With Problem ...' failed due to the following reason: 905.76/297.03 905.76/297.03 Empty strict component of the problem is NOT empty. 905.76/297.03 905.76/297.03 905.76/297.03 905.76/297.03 905.76/297.03 905.76/297.03 2) 'Best' failed due to the following reason: 905.76/297.03 905.76/297.03 None of the processors succeeded. 905.76/297.03 905.76/297.03 Details of failed attempt(s): 905.76/297.03 ----------------------------- 905.76/297.03 1) 'bsearch-popstar (timeout of 297 seconds)' failed due to the 905.76/297.03 following reason: 905.76/297.03 905.76/297.03 The processor is inapplicable, reason: 905.76/297.03 Processor only applicable for innermost runtime complexity analysis 905.76/297.03 905.76/297.03 2) 'Polynomial Path Order (PS) (timeout of 297 seconds)' failed due 905.76/297.03 to the following reason: 905.76/297.03 905.76/297.03 The processor is inapplicable, reason: 905.76/297.03 Processor only applicable for innermost runtime complexity analysis 905.76/297.03 905.76/297.03 905.76/297.03 3) 'Fastest (timeout of 24 seconds) (timeout of 297 seconds)' 905.76/297.03 failed due to the following reason: 905.76/297.03 905.76/297.03 None of the processors succeeded. 905.76/297.03 905.76/297.03 Details of failed attempt(s): 905.76/297.03 ----------------------------- 905.76/297.03 1) 'Bounds with minimal-enrichment and initial automaton 'match'' 905.76/297.03 failed due to the following reason: 905.76/297.03 905.76/297.03 match-boundness of the problem could not be verified. 905.76/297.03 905.76/297.03 2) 'Bounds with perSymbol-enrichment and initial automaton 'match'' 905.76/297.03 failed due to the following reason: 905.76/297.03 905.76/297.03 match-boundness of the problem could not be verified. 905.76/297.03 905.76/297.03 905.76/297.03 905.76/297.03 3) 'Weak Dependency Pairs (timeout of 297 seconds)' failed due to 905.76/297.03 the following reason: 905.76/297.03 905.76/297.03 We add the following weak dependency pairs: 905.76/297.03 905.76/297.03 Strict DPs: 905.76/297.03 { *^#(x, +(y, f(z))) -> c_1(*^#(g(x, z), +(y, y))) 905.76/297.03 , *^#(*(x, y), z) -> c_2(*^#(x, *(y, z))) 905.76/297.03 , *^#(+(x, y), z) -> c_3(*^#(x, z), *^#(y, z)) } 905.76/297.03 905.76/297.03 and mark the set of starting terms. 905.76/297.03 905.76/297.03 We are left with following problem, upon which TcT provides the 905.76/297.03 certificate MAYBE. 905.76/297.03 905.76/297.03 Strict DPs: 905.76/297.03 { *^#(x, +(y, f(z))) -> c_1(*^#(g(x, z), +(y, y))) 905.76/297.03 , *^#(*(x, y), z) -> c_2(*^#(x, *(y, z))) 905.76/297.03 , *^#(+(x, y), z) -> c_3(*^#(x, z), *^#(y, z)) } 905.76/297.03 Strict Trs: 905.76/297.03 { *(x, +(y, f(z))) -> *(g(x, z), +(y, y)) 905.76/297.03 , *(*(x, y), z) -> *(x, *(y, z)) 905.76/297.03 , *(+(x, y), z) -> +(*(x, z), *(y, z)) } 905.76/297.03 Obligation: 905.76/297.03 runtime complexity 905.76/297.03 Answer: 905.76/297.03 MAYBE 905.76/297.03 905.76/297.03 Empty strict component of the problem is NOT empty. 905.76/297.03 905.76/297.03 905.76/297.03 Arrrr.. 906.38/297.67 EOF