MAYBE

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

Strict Trs:
  { f(X, X) -> f(a(), b())
  , b() -> a() }
Obligation:
  innermost runtime complexity
Answer:
  MAYBE

We add following weak dependency pairs:

Strict DPs:
  { f^#(X, X) -> c_1(f^#(a(), b()))
  , b^#() -> c_2() }

and mark the set of starting terms.

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

Strict DPs:
  { f^#(X, X) -> c_1(f^#(a(), b()))
  , b^#() -> c_2() }
Strict Trs:
  { f(X, X) -> f(a(), b())
  , b() -> a() }
Obligation:
  innermost runtime complexity
Answer:
  MAYBE

We replace rewrite rules by usable rules:

  Strict Usable Rules: { b() -> a() }

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

Strict DPs:
  { f^#(X, X) -> c_1(f^#(a(), b()))
  , b^#() -> c_2() }
Strict Trs: { b() -> a() }
Obligation:
  innermost runtime complexity
Answer:
  MAYBE

The weightgap principle applies (using the following constant
growth matrix-interpretation)

The following argument positions are usable:
  Uargs(f^#) = {2}, Uargs(c_1) = {1}

TcT has computed following constructor-restricted matrix
interpretation.

            [a] = [1]                  
                                       
            [b] = [2]                  
                                       
  [f^#](x1, x2) = [2] x1 + [1] x2 + [2]
                                       
      [c_1](x1) = [1] x1 + [1]         
                                       
          [b^#] = [1]                  
                                       
          [c_2] = [2]                  

This order satisfies following ordering constraints:

  [b()] = [2]  
        > [1]  
        = [a()]
               

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 DPs:
  { f^#(X, X) -> c_1(f^#(a(), b()))
  , b^#() -> c_2() }
Weak Trs: { b() -> a() }
Obligation:
  innermost runtime complexity
Answer:
  MAYBE

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

  DPs:
    { 1: f^#(X, X) -> c_1(f^#(a(), b()))
    , 2: b^#() -> c_2() }

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

Strict DPs: { f^#(X, X) -> c_1(f^#(a(), b())) }
Weak DPs: { b^#() -> c_2() }
Weak Trs: { b() -> a() }
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.

{ b^#() -> c_2() }

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

Strict DPs: { f^#(X, X) -> c_1(f^#(a(), b())) }
Weak Trs: { b() -> a() }
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..