MAYBE We are left with following problem, upon which TcT provides the certificate MAYBE. Strict Trs: { a__h(X) -> a__g(mark(X), X) , a__h(X) -> h(X) , a__g(X1, X2) -> g(X1, X2) , a__g(a(), X) -> a__f(b(), X) , mark(a()) -> a__a() , mark(b()) -> b() , mark(h(X)) -> a__h(mark(X)) , mark(g(X1, X2)) -> a__g(mark(X1), X2) , mark(f(X1, X2)) -> a__f(mark(X1), X2) , a__f(X, X) -> a__h(a__a()) , a__f(X1, X2) -> f(X1, X2) , a__a() -> a() , a__a() -> b() } 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: 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) 'Polynomial Path Order (PS) (timeout of 60 seconds)' failed due to the following reason: The input cannot be shown compatible 2) 'bsearch-popstar (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..