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