MAYBE

We are left with following problem, upon which TcT provides the
certificate MAYBE.

Strict Trs:
  { f(true(), x, y) -> f(gt(x, y), s(x), s(s(y)))
  , gt(s(u), s(v)) -> gt(u, v)
  , gt(s(u), 0()) -> true()
  , gt(0(), v) -> false() }
Obligation:
  innermost runtime complexity
Answer:
  MAYBE

We add following dependency tuples:

Strict DPs:
  { f^#(true(), x, y) ->
    c_1(f^#(gt(x, y), s(x), s(s(y))), gt^#(x, y))
  , gt^#(s(u), s(v)) -> c_2(gt^#(u, v))
  , gt^#(s(u), 0()) -> c_3()
  , gt^#(0(), v) -> c_4() }

and mark the set of starting terms.

We are left with following problem, upon which TcT provides the
certificate MAYBE.

Strict DPs:
  { f^#(true(), x, y) ->
    c_1(f^#(gt(x, y), s(x), s(s(y))), gt^#(x, y))
  , gt^#(s(u), s(v)) -> c_2(gt^#(u, v))
  , gt^#(s(u), 0()) -> c_3()
  , gt^#(0(), v) -> c_4() }
Weak Trs:
  { f(true(), x, y) -> f(gt(x, y), s(x), s(s(y)))
  , gt(s(u), s(v)) -> gt(u, v)
  , gt(s(u), 0()) -> true()
  , gt(0(), v) -> false() }
Obligation:
  innermost runtime complexity
Answer:
  MAYBE

We estimate the number of application of {3,4} by applications of
Pre({3,4}) = {1,2}. Here rules are labeled as follows:

  DPs:
    { 1: f^#(true(), x, y) ->
         c_1(f^#(gt(x, y), s(x), s(s(y))), gt^#(x, y))
    , 2: gt^#(s(u), s(v)) -> c_2(gt^#(u, v))
    , 3: gt^#(s(u), 0()) -> c_3()
    , 4: gt^#(0(), v) -> c_4() }

We are left with following problem, upon which TcT provides the
certificate MAYBE.

Strict DPs:
  { f^#(true(), x, y) ->
    c_1(f^#(gt(x, y), s(x), s(s(y))), gt^#(x, y))
  , gt^#(s(u), s(v)) -> c_2(gt^#(u, v)) }
Weak DPs:
  { gt^#(s(u), 0()) -> c_3()
  , gt^#(0(), v) -> c_4() }
Weak Trs:
  { f(true(), x, y) -> f(gt(x, y), s(x), s(s(y)))
  , gt(s(u), s(v)) -> gt(u, v)
  , gt(s(u), 0()) -> true()
  , gt(0(), v) -> false() }
Obligation:
  innermost runtime complexity
Answer:
  MAYBE

The following weak DPs constitute a sub-graph of the DG that is
closed under successors. The DPs are removed.

{ gt^#(s(u), 0()) -> c_3()
, gt^#(0(), v) -> c_4() }

We are left with following problem, upon which TcT provides the
certificate MAYBE.

Strict DPs:
  { f^#(true(), x, y) ->
    c_1(f^#(gt(x, y), s(x), s(s(y))), gt^#(x, y))
  , gt^#(s(u), s(v)) -> c_2(gt^#(u, v)) }
Weak Trs:
  { f(true(), x, y) -> f(gt(x, y), s(x), s(s(y)))
  , gt(s(u), s(v)) -> gt(u, v)
  , gt(s(u), 0()) -> true()
  , gt(0(), v) -> false() }
Obligation:
  innermost runtime complexity
Answer:
  MAYBE

We replace rewrite rules by usable rules:

  Weak Usable Rules:
    { gt(s(u), s(v)) -> gt(u, v)
    , gt(s(u), 0()) -> true()
    , gt(0(), v) -> false() }

We are left with following problem, upon which TcT provides the
certificate MAYBE.

Strict DPs:
  { f^#(true(), x, y) ->
    c_1(f^#(gt(x, y), s(x), s(s(y))), gt^#(x, y))
  , gt^#(s(u), s(v)) -> c_2(gt^#(u, v)) }
Weak Trs:
  { gt(s(u), s(v)) -> gt(u, v)
  , gt(s(u), 0()) -> true()
  , gt(0(), v) -> false() }
Obligation:
  innermost runtime complexity
Answer:
  MAYBE

None of the processors succeeded.

Details of failed attempt(s):
-----------------------------
1) 'matrices' failed due to the following reason:
   
   None of the processors succeeded.
   
   Details of failed attempt(s):
   -----------------------------
   1) 'matrix interpretation of dimension 4' failed due to the
      following reason:
      
      The input cannot be shown compatible
   
   2) 'matrix interpretation of dimension 3' failed due to the
      following reason:
      
      The input cannot be shown compatible
   
   3) 'matrix interpretation of dimension 3' failed due to the
      following reason:
      
      The input cannot be shown compatible
   
   4) 'matrix interpretation of dimension 2' failed due to the
      following reason:
      
      The input cannot be shown compatible
   
   5) 'matrix interpretation of dimension 2' failed due to the
      following reason:
      
      The input cannot be shown compatible
   
   6) 'matrix interpretation of dimension 1' failed due to the
      following reason:
      
      The input cannot be shown compatible
   

2) 'empty' failed due to the following reason:
   
   Empty strict component of the problem is NOT empty.


Arrrr..