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