MAYBE We are left with following problem, upon which TcT provides the certificate MAYBE. Strict Trs: { minus(x, y) -> cond(ge(x, s(y)), x, y) , cond(false(), x, y) -> 0() , cond(true(), x, y) -> s(minus(x, s(y))) , ge(u, 0()) -> true() , ge(s(u), s(v)) -> ge(u, v) , ge(0(), s(v)) -> false() } 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) '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) '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) '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, y) -> c_1(cond^#(ge(x, s(y)), x, y)) , cond^#(false(), x, y) -> c_2() , cond^#(true(), x, y) -> c_3(minus^#(x, s(y))) , ge^#(u, 0()) -> c_4() , ge^#(s(u), s(v)) -> c_5(ge^#(u, v)) , ge^#(0(), s(v)) -> c_6() } and mark the set of starting terms. We are left with following problem, upon which TcT provides the certificate MAYBE. Strict DPs: { minus^#(x, y) -> c_1(cond^#(ge(x, s(y)), x, y)) , cond^#(false(), x, y) -> c_2() , cond^#(true(), x, y) -> c_3(minus^#(x, s(y))) , ge^#(u, 0()) -> c_4() , ge^#(s(u), s(v)) -> c_5(ge^#(u, v)) , ge^#(0(), s(v)) -> c_6() } Strict Trs: { minus(x, y) -> cond(ge(x, s(y)), x, y) , cond(false(), x, y) -> 0() , cond(true(), x, y) -> s(minus(x, s(y))) , ge(u, 0()) -> true() , ge(s(u), s(v)) -> ge(u, v) , ge(0(), s(v)) -> false() } Obligation: runtime complexity Answer: MAYBE We estimate the number of application of {2,4,6} by applications of Pre({2,4,6}) = {1,5}. Here rules are labeled as follows: DPs: { 1: minus^#(x, y) -> c_1(cond^#(ge(x, s(y)), x, y)) , 2: cond^#(false(), x, y) -> c_2() , 3: cond^#(true(), x, y) -> c_3(minus^#(x, s(y))) , 4: ge^#(u, 0()) -> c_4() , 5: ge^#(s(u), s(v)) -> c_5(ge^#(u, v)) , 6: ge^#(0(), s(v)) -> c_6() } We are left with following problem, upon which TcT provides the certificate MAYBE. Strict DPs: { minus^#(x, y) -> c_1(cond^#(ge(x, s(y)), x, y)) , cond^#(true(), x, y) -> c_3(minus^#(x, s(y))) , ge^#(s(u), s(v)) -> c_5(ge^#(u, v)) } Strict Trs: { minus(x, y) -> cond(ge(x, s(y)), x, y) , cond(false(), x, y) -> 0() , cond(true(), x, y) -> s(minus(x, s(y))) , ge(u, 0()) -> true() , ge(s(u), s(v)) -> ge(u, v) , ge(0(), s(v)) -> false() } Weak DPs: { cond^#(false(), x, y) -> c_2() , ge^#(u, 0()) -> c_4() , ge^#(0(), s(v)) -> c_6() } Obligation: runtime complexity Answer: MAYBE Empty strict component of the problem is NOT empty. Arrrr..