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