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