MAYBE We are left with following problem, upon which TcT provides the certificate MAYBE. Strict Trs: { cond(true(), x) -> cond(odd(x), p(x)) , odd(0()) -> false() , odd(s(0())) -> true() , odd(s(s(x))) -> odd(x) , p(0()) -> 0() , p(s(x)) -> x } Obligation: innermost runtime complexity Answer: MAYBE None of the processors succeeded. Details of failed attempt(s): ----------------------------- 1) 'empty' failed due to the following reason: Empty strict component of the problem is NOT empty. 2) 'Best' failed due to the following reason: 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: The weightgap principle applies (using the following nonconstant growth matrix-interpretation) The following argument positions are usable: Uargs(cond) = {1, 2} TcT has computed the following matrix interpretation satisfying not(EDA) and not(IDA(1)). [cond](x1, x2) = [1] x1 + [1] x2 + [1] [true] = [7] [odd](x1) = [7] [p](x1) = [1] x1 + [7] [0] = [7] [false] = [6] [s](x1) = [1] x1 + [7] The following symbols are considered usable {cond, odd, p} The order satisfies the following ordering constraints: [cond(true(), x)] = [1] x + [8] ? [1] x + [15] = [cond(odd(x), p(x))] [odd(0())] = [7] > [6] = [false()] [odd(s(0()))] = [7] >= [7] = [true()] [odd(s(s(x)))] = [7] >= [7] = [odd(x)] [p(0())] = [14] > [7] = [0()] [p(s(x))] = [1] x + [14] > [1] x + [0] = [x] Further, it can be verified that all rules not oriented are covered by the weightgap condition. We are left with following problem, upon which TcT provides the certificate MAYBE. Strict Trs: { cond(true(), x) -> cond(odd(x), p(x)) , odd(s(0())) -> true() , odd(s(s(x))) -> odd(x) } Weak Trs: { odd(0()) -> false() , p(0()) -> 0() , p(s(x)) -> x } Obligation: innermost runtime complexity Answer: MAYBE The weightgap principle applies (using the following nonconstant growth matrix-interpretation) The following argument positions are usable: Uargs(cond) = {1, 2} TcT has computed the following matrix interpretation satisfying not(EDA) and not(IDA(1)). [cond](x1, x2) = [1] x1 + [1] x2 + [0] [true] = [1] [odd](x1) = [4] [p](x1) = [1] x1 + [4] [0] = [3] [false] = [4] [s](x1) = [1] x1 + [7] The following symbols are considered usable {cond, odd, p} The order satisfies the following ordering constraints: [cond(true(), x)] = [1] x + [1] ? [1] x + [8] = [cond(odd(x), p(x))] [odd(0())] = [4] >= [4] = [false()] [odd(s(0()))] = [4] > [1] = [true()] [odd(s(s(x)))] = [4] >= [4] = [odd(x)] [p(0())] = [7] > [3] = [0()] [p(s(x))] = [1] x + [11] > [1] x + [0] = [x] Further, it can be verified that all rules not oriented are covered by the weightgap condition. We are left with following problem, upon which TcT provides the certificate MAYBE. Strict Trs: { cond(true(), x) -> cond(odd(x), p(x)) , odd(s(s(x))) -> odd(x) } Weak Trs: { odd(0()) -> false() , odd(s(0())) -> true() , p(0()) -> 0() , p(s(x)) -> x } Obligation: innermost runtime complexity Answer: MAYBE None of the processors succeeded. Details of failed attempt(s): ----------------------------- 1) 'empty' failed due to the following reason: Empty strict component of the problem is NOT empty. 2) 'WithProblem' failed due to the following reason: None of the processors succeeded. Details of failed attempt(s): ----------------------------- 1) 'empty' failed due to the following reason: Empty strict component of the problem is NOT empty. 2) 'Fastest' failed due to the following reason: None of the processors succeeded. Details of failed attempt(s): ----------------------------- 1) 'WithProblem' failed due to the following reason: None of the processors succeeded. Details of failed attempt(s): ----------------------------- 1) 'empty' failed due to the following reason: Empty strict component of the problem is NOT empty. 2) 'WithProblem' failed due to the following reason: None of the processors succeeded. Details of failed attempt(s): ----------------------------- 1) 'empty' failed due to the following reason: Empty strict component of the problem is NOT empty. 2) 'WithProblem' failed due to the following reason: None of the processors succeeded. Details of failed attempt(s): ----------------------------- 1) 'empty' failed due to the following reason: Empty strict component of the problem is NOT empty. 2) 'WithProblem' failed due to the following reason: Empty strict component of the problem is NOT empty. 2) 'WithProblem' failed due to the following reason: None of the processors succeeded. Details of failed attempt(s): ----------------------------- 1) 'empty' failed due to the following reason: Empty strict component of the problem is NOT empty. 2) 'WithProblem' failed due to the following reason: Empty strict component of the problem is NOT empty. 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 input cannot be shown compatible 2) 'Polynomial Path Order (PS) (timeout of 60 seconds)' failed due to the following reason: The input cannot be shown compatible 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 minimal-enrichment and initial automaton 'match'' failed due to the following reason: match-boundness of the problem could not be verified. 2) 'Bounds with perSymbol-enrichment and initial automaton 'match'' failed due to the following reason: match-boundness of the problem could not be verified. Arrrr..