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