Problem Der95 12

Tool CaT

Execution TimeUnknown
Answer
MAYBE
InputDer95 12

stdout:

MAYBE

Problem:
 not(not(x)) -> x
 not(or(x,y)) -> and(not(x),not(y))
 not(and(x,y)) -> or(not(x),not(y))
 and(x,or(y,z)) -> or(and(x,y),and(x,z))
 and(or(y,z),x) -> or(and(x,y),and(x,z))

Proof:
 Open

Tool IRC1

Execution TimeUnknown
Answer
MAYBE
InputDer95 12

stdout:

MAYBE

Tool IRC2

Execution TimeUnknown
Answer
MAYBE
InputDer95 12

stdout:

MAYBE

'Fastest (timeout of 60.0 seconds)'
-----------------------------------
Answer:           MAYBE
Input Problem:    innermost runtime-complexity with respect to
  Rules:
    {  not(not(x)) -> x
     , not(or(x, y)) -> and(not(x), not(y))
     , not(and(x, y)) -> or(not(x), not(y))
     , and(x, or(y, z)) -> or(and(x, y), and(x, z))
     , and(or(y, z), x) -> or(and(x, y), and(x, z))}

Proof Output:    
  None of the processors succeeded.
  
  Details of failed attempt(s):
  -----------------------------
    1) 'wdg' failed due to the following reason:
         Transformation Details:
         -----------------------
           We have computed the following set of weak (innermost) dependency pairs:
           
             {  1: not^#(not(x)) -> c_0()
              , 2: not^#(or(x, y)) -> c_1(and^#(not(x), not(y)))
              , 3: not^#(and(x, y)) -> c_2(not^#(x), not^#(y))
              , 4: and^#(x, or(y, z)) -> c_3(and^#(x, y), and^#(x, z))
              , 5: and^#(or(y, z), x) -> c_4(and^#(x, y), and^#(x, z))}
           
           Following Dependency Graph (modulo SCCs) was computed. (Answers to
           subproofs are indicated to the right.)
           
             ->{3}                                                       [     inherited      ]
                |
                |->{1}                                                   [    YES(?,O(1))     ]
                |
                `->{2}                                                   [     inherited      ]
                    |
                    `->{5,4}                                             [         NA         ]
             
           
         
         Sub-problems:
         -------------
           * Path {3}: inherited
             -------------------
             
             This path is subsumed by the proof of path {3}->{2}->{5,4}.
           
           * Path {3}->{1}: YES(?,O(1))
             --------------------------
             
             The usable rules of this path are empty.
             
             The weightgap principle applies, using the following adequate RMI:
               The following argument positions are usable:
                 Uargs(not) = {}, Uargs(or) = {}, Uargs(and) = {},
                 Uargs(not^#) = {}, Uargs(c_1) = {}, Uargs(and^#) = {},
                 Uargs(c_2) = {1, 2}, Uargs(c_3) = {}, Uargs(c_4) = {}
               We have the following constructor-restricted matrix interpretation:
               Interpretation Functions:
                not(x1) = [0 0 0] x1 + [0]
                          [0 0 0]      [0]
                          [0 0 0]      [0]
                or(x1, x2) = [0 0 0] x1 + [0 0 0] x2 + [0]
                             [0 0 0]      [0 0 0]      [0]
                             [0 0 0]      [0 0 0]      [0]
                and(x1, x2) = [0 0 0] x1 + [0 0 0] x2 + [0]
                              [0 0 0]      [0 0 0]      [0]
                              [0 0 0]      [0 0 0]      [0]
                not^#(x1) = [0 0 0] x1 + [0]
                            [0 0 0]      [0]
                            [0 0 0]      [0]
                c_0() = [0]
                        [0]
                        [0]
                c_1(x1) = [0 0 0] x1 + [0]
                          [0 0 0]      [0]
                          [0 0 0]      [0]
                and^#(x1, x2) = [0 0 0] x1 + [0 0 0] x2 + [0]
                                [0 0 0]      [0 0 0]      [0]
                                [0 0 0]      [0 0 0]      [0]
                c_2(x1, x2) = [1 0 0] x1 + [1 0 0] x2 + [0]
                              [0 1 0]      [0 1 0]      [0]
                              [0 0 1]      [0 0 1]      [0]
                c_3(x1, x2) = [0 0 0] x1 + [0 0 0] x2 + [0]
                              [0 0 0]      [0 0 0]      [0]
                              [0 0 0]      [0 0 0]      [0]
                c_4(x1, x2) = [0 0 0] x1 + [0 0 0] x2 + [0]
                              [0 0 0]      [0 0 0]      [0]
                              [0 0 0]      [0 0 0]      [0]
             
             We apply the sub-processor on the resulting sub-problem:
             
             'matrix-interpretation of dimension 3'
             --------------------------------------
             Answer:           YES(?,O(1))
             Input Problem:    innermost DP runtime-complexity with respect to
               Strict Rules: {not^#(not(x)) -> c_0()}
               Weak Rules: {not^#(and(x, y)) -> c_2(not^#(x), not^#(y))}
             
             Proof Output:    
               The following argument positions are usable:
                 Uargs(not) = {}, Uargs(and) = {}, Uargs(not^#) = {},
                 Uargs(c_2) = {1, 2}
               We have the following constructor-restricted matrix interpretation:
               Interpretation Functions:
                not(x1) = [0 0 0] x1 + [2]
                          [0 0 0]      [2]
                          [0 0 0]      [0]
                and(x1, x2) = [6 2 2] x1 + [0 3 0] x2 + [0]
                              [0 4 2]      [4 1 0]      [6]
                              [0 0 0]      [0 0 0]      [0]
                not^#(x1) = [2 2 0] x1 + [0]
                            [0 0 0]      [2]
                            [0 2 0]      [2]
                c_0() = [1]
                        [0]
                        [0]
                c_2(x1, x2) = [4 2 2] x1 + [3 0 1] x2 + [1]
                              [0 0 0]      [0 0 0]      [2]
                              [0 0 0]      [0 0 0]      [6]
           
           * Path {3}->{2}: inherited
             ------------------------
             
             This path is subsumed by the proof of path {3}->{2}->{5,4}.
           
           * Path {3}->{2}->{5,4}: NA
             ------------------------
             
             The usable rules for this path are:
             
               {  not(not(x)) -> x
                , not(or(x, y)) -> and(not(x), not(y))
                , not(and(x, y)) -> or(not(x), not(y))
                , and(x, or(y, z)) -> or(and(x, y), and(x, z))
                , and(or(y, z), x) -> or(and(x, y), and(x, z))}
             
             The weight gap principle does not apply:
               The input cannot be shown compatible
             Complexity induced by the adequate RMI: MAYBE
             
             We have not generated a proof for the resulting sub-problem.
    
    2) 'wdg' failed due to the following reason:
         Transformation Details:
         -----------------------
           We have computed the following set of weak (innermost) dependency pairs:
           
             {  1: not^#(not(x)) -> c_0()
              , 2: not^#(or(x, y)) -> c_1(and^#(not(x), not(y)))
              , 3: not^#(and(x, y)) -> c_2(not^#(x), not^#(y))
              , 4: and^#(x, or(y, z)) -> c_3(and^#(x, y), and^#(x, z))
              , 5: and^#(or(y, z), x) -> c_4(and^#(x, y), and^#(x, z))}
           
           Following Dependency Graph (modulo SCCs) was computed. (Answers to
           subproofs are indicated to the right.)
           
             ->{3}                                                       [     inherited      ]
                |
                |->{1}                                                   [    YES(?,O(1))     ]
                |
                `->{2}                                                   [     inherited      ]
                    |
                    `->{5,4}                                             [       MAYBE        ]
             
           
         
         Sub-problems:
         -------------
           * Path {3}: inherited
             -------------------
             
             This path is subsumed by the proof of path {3}->{2}->{5,4}.
           
           * Path {3}->{1}: YES(?,O(1))
             --------------------------
             
             The usable rules of this path are empty.
             
             The weightgap principle applies, using the following adequate RMI:
               The following argument positions are usable:
                 Uargs(not) = {}, Uargs(or) = {}, Uargs(and) = {},
                 Uargs(not^#) = {}, Uargs(c_1) = {}, Uargs(and^#) = {},
                 Uargs(c_2) = {1, 2}, Uargs(c_3) = {}, Uargs(c_4) = {}
               We have the following constructor-restricted matrix interpretation:
               Interpretation Functions:
                not(x1) = [0 0] x1 + [0]
                          [0 0]      [0]
                or(x1, x2) = [0 0] x1 + [0 0] x2 + [0]
                             [0 0]      [0 0]      [0]
                and(x1, x2) = [0 0] x1 + [0 0] x2 + [0]
                              [0 0]      [0 0]      [0]
                not^#(x1) = [0 0] x1 + [0]
                            [0 0]      [0]
                c_0() = [0]
                        [0]
                c_1(x1) = [0 0] x1 + [0]
                          [0 0]      [0]
                and^#(x1, x2) = [0 0] x1 + [0 0] x2 + [0]
                                [0 0]      [0 0]      [0]
                c_2(x1, x2) = [1 0] x1 + [1 0] x2 + [0]
                              [0 1]      [0 1]      [0]
                c_3(x1, x2) = [0 0] x1 + [0 0] x2 + [0]
                              [0 0]      [0 0]      [0]
                c_4(x1, x2) = [0 0] x1 + [0 0] x2 + [0]
                              [0 0]      [0 0]      [0]
             
             We apply the sub-processor on the resulting sub-problem:
             
             'matrix-interpretation of dimension 2'
             --------------------------------------
             Answer:           YES(?,O(1))
             Input Problem:    innermost DP runtime-complexity with respect to
               Strict Rules: {not^#(not(x)) -> c_0()}
               Weak Rules: {not^#(and(x, y)) -> c_2(not^#(x), not^#(y))}
             
             Proof Output:    
               The following argument positions are usable:
                 Uargs(not) = {}, Uargs(and) = {}, Uargs(not^#) = {},
                 Uargs(c_2) = {1, 2}
               We have the following constructor-restricted matrix interpretation:
               Interpretation Functions:
                not(x1) = [0 0] x1 + [0]
                          [0 0]      [2]
                and(x1, x2) = [6 2] x1 + [4 2] x2 + [2]
                              [0 2]      [2 2]      [2]
                not^#(x1) = [2 2] x1 + [0]
                            [2 2]      [0]
                c_0() = [1]
                        [0]
                c_2(x1, x2) = [2 2] x1 + [2 2] x2 + [6]
                              [0 0]      [1 3]      [7]
           
           * Path {3}->{2}: inherited
             ------------------------
             
             This path is subsumed by the proof of path {3}->{2}->{5,4}.
           
           * Path {3}->{2}->{5,4}: MAYBE
             ---------------------------
             
             The usable rules for this path are:
             
               {  not(not(x)) -> x
                , not(or(x, y)) -> and(not(x), not(y))
                , not(and(x, y)) -> or(not(x), not(y))
                , and(x, or(y, z)) -> or(and(x, y), and(x, z))
                , and(or(y, z), x) -> or(and(x, y), and(x, z))}
             
             The weight gap principle does not apply:
               The input cannot be shown compatible
             Complexity induced by the adequate RMI: MAYBE
             
             We apply the sub-processor on the resulting sub-problem:
             
             'matrix-interpretation of dimension 2'
             --------------------------------------
             Answer:           MAYBE
             Input Problem:    innermost runtime-complexity with respect to
               Rules:
                 {  not^#(or(x, y)) -> c_1(and^#(not(x), not(y)))
                  , not^#(and(x, y)) -> c_2(not^#(x), not^#(y))
                  , and^#(or(y, z), x) -> c_4(and^#(x, y), and^#(x, z))
                  , and^#(x, or(y, z)) -> c_3(and^#(x, y), and^#(x, z))
                  , not(not(x)) -> x
                  , not(or(x, y)) -> and(not(x), not(y))
                  , not(and(x, y)) -> or(not(x), not(y))
                  , and(x, or(y, z)) -> or(and(x, y), and(x, z))
                  , and(or(y, z), x) -> or(and(x, y), and(x, z))}
             
             Proof Output:    
               The input cannot be shown compatible
    
    3) 'wdg' failed due to the following reason:
         Transformation Details:
         -----------------------
           We have computed the following set of weak (innermost) dependency pairs:
           
             {  1: not^#(not(x)) -> c_0()
              , 2: not^#(or(x, y)) -> c_1(and^#(not(x), not(y)))
              , 3: not^#(and(x, y)) -> c_2(not^#(x), not^#(y))
              , 4: and^#(x, or(y, z)) -> c_3(and^#(x, y), and^#(x, z))
              , 5: and^#(or(y, z), x) -> c_4(and^#(x, y), and^#(x, z))}
           
           Following Dependency Graph (modulo SCCs) was computed. (Answers to
           subproofs are indicated to the right.)
           
             ->{3}                                                       [     inherited      ]
                |
                |->{1}                                                   [    YES(?,O(1))     ]
                |
                `->{2}                                                   [     inherited      ]
                    |
                    `->{5,4}                                             [       MAYBE        ]
             
           
         
         Sub-problems:
         -------------
           * Path {3}: inherited
             -------------------
             
             This path is subsumed by the proof of path {3}->{2}->{5,4}.
           
           * Path {3}->{1}: YES(?,O(1))
             --------------------------
             
             The usable rules of this path are empty.
             
             The weightgap principle applies, using the following adequate RMI:
               The following argument positions are usable:
                 Uargs(not) = {}, Uargs(or) = {}, Uargs(and) = {},
                 Uargs(not^#) = {}, Uargs(c_1) = {}, Uargs(and^#) = {},
                 Uargs(c_2) = {1, 2}, Uargs(c_3) = {}, Uargs(c_4) = {}
               We have the following constructor-restricted matrix interpretation:
               Interpretation Functions:
                not(x1) = [0] x1 + [0]
                or(x1, x2) = [0] x1 + [0] x2 + [0]
                and(x1, x2) = [0] x1 + [0] x2 + [0]
                not^#(x1) = [0] x1 + [0]
                c_0() = [0]
                c_1(x1) = [0] x1 + [0]
                and^#(x1, x2) = [0] x1 + [0] x2 + [0]
                c_2(x1, x2) = [1] x1 + [1] x2 + [0]
                c_3(x1, x2) = [0] x1 + [0] x2 + [0]
                c_4(x1, x2) = [0] x1 + [0] x2 + [0]
             
             We apply the sub-processor on the resulting sub-problem:
             
             'matrix-interpretation of dimension 1'
             --------------------------------------
             Answer:           YES(?,O(1))
             Input Problem:    innermost DP runtime-complexity with respect to
               Strict Rules: {not^#(not(x)) -> c_0()}
               Weak Rules: {not^#(and(x, y)) -> c_2(not^#(x), not^#(y))}
             
             Proof Output:    
               The following argument positions are usable:
                 Uargs(not) = {}, Uargs(and) = {}, Uargs(not^#) = {},
                 Uargs(c_2) = {1, 2}
               We have the following constructor-restricted matrix interpretation:
               Interpretation Functions:
                not(x1) = [0] x1 + [2]
                and(x1, x2) = [2] x1 + [2] x2 + [2]
                not^#(x1) = [2] x1 + [2]
                c_0() = [1]
                c_2(x1, x2) = [1] x1 + [2] x2 + [0]
           
           * Path {3}->{2}: inherited
             ------------------------
             
             This path is subsumed by the proof of path {3}->{2}->{5,4}.
           
           * Path {3}->{2}->{5,4}: MAYBE
             ---------------------------
             
             The usable rules for this path are:
             
               {  not(not(x)) -> x
                , not(or(x, y)) -> and(not(x), not(y))
                , not(and(x, y)) -> or(not(x), not(y))
                , and(x, or(y, z)) -> or(and(x, y), and(x, z))
                , and(or(y, z), x) -> or(and(x, y), and(x, z))}
             
             The weight gap principle does not apply:
               The input cannot be shown compatible
             Complexity induced by the adequate RMI: MAYBE
             
             We apply the sub-processor on the resulting sub-problem:
             
             'matrix-interpretation of dimension 1'
             --------------------------------------
             Answer:           MAYBE
             Input Problem:    innermost runtime-complexity with respect to
               Rules:
                 {  not^#(or(x, y)) -> c_1(and^#(not(x), not(y)))
                  , not^#(and(x, y)) -> c_2(not^#(x), not^#(y))
                  , and^#(or(y, z), x) -> c_4(and^#(x, y), and^#(x, z))
                  , and^#(x, or(y, z)) -> c_3(and^#(x, y), and^#(x, z))
                  , not(not(x)) -> x
                  , not(or(x, y)) -> and(not(x), not(y))
                  , not(and(x, y)) -> or(not(x), not(y))
                  , and(x, or(y, z)) -> or(and(x, y), and(x, z))
                  , and(or(y, z), x) -> or(and(x, y), and(x, z))}
             
             Proof Output:    
               The input cannot be shown compatible
    
    4) 'matrix-interpretation of dimension 1' failed due to the following reason:
         The input cannot be shown compatible
    
    5) 'Bounds with perSymbol-enrichment and initial automaton 'match'' failed due to the following reason:
         match-boundness of the problem could not be verified.
    
    6) 'Bounds with minimal-enrichment and initial automaton 'match'' failed due to the following reason:
         match-boundness of the problem could not be verified.
    

Tool RC1

Execution TimeUnknown
Answer
MAYBE
InputDer95 12

stdout:

MAYBE

Tool RC2

Execution TimeUnknown
Answer
MAYBE
InputDer95 12

stdout:

MAYBE

'Fastest (timeout of 60.0 seconds)'
-----------------------------------
Answer:           MAYBE
Input Problem:    runtime-complexity with respect to
  Rules:
    {  not(not(x)) -> x
     , not(or(x, y)) -> and(not(x), not(y))
     , not(and(x, y)) -> or(not(x), not(y))
     , and(x, or(y, z)) -> or(and(x, y), and(x, z))
     , and(or(y, z), x) -> or(and(x, y), and(x, z))}

Proof Output:    
  None of the processors succeeded.
  
  Details of failed attempt(s):
  -----------------------------
    1) 'wdg' failed due to the following reason:
         Transformation Details:
         -----------------------
           We have computed the following set of weak (innermost) dependency pairs:
           
             {  1: not^#(not(x)) -> c_0(x)
              , 2: not^#(or(x, y)) -> c_1(and^#(not(x), not(y)))
              , 3: not^#(and(x, y)) -> c_2(not^#(x), not^#(y))
              , 4: and^#(x, or(y, z)) -> c_3(and^#(x, y), and^#(x, z))
              , 5: and^#(or(y, z), x) -> c_4(and^#(x, y), and^#(x, z))}
           
           Following Dependency Graph (modulo SCCs) was computed. (Answers to
           subproofs are indicated to the right.)
           
             ->{3}                                                       [     inherited      ]
                |
                |->{1}                                                   [    YES(?,O(1))     ]
                |
                `->{2}                                                   [     inherited      ]
                    |
                    `->{5,4}                                             [         NA         ]
             
           
         
         Sub-problems:
         -------------
           * Path {3}: inherited
             -------------------
             
             This path is subsumed by the proof of path {3}->{2}->{5,4}.
           
           * Path {3}->{1}: YES(?,O(1))
             --------------------------
             
             The usable rules of this path are empty.
             
             The weightgap principle applies, using the following adequate RMI:
               The following argument positions are usable:
                 Uargs(not) = {}, Uargs(or) = {}, Uargs(and) = {},
                 Uargs(not^#) = {}, Uargs(c_0) = {}, Uargs(c_1) = {},
                 Uargs(and^#) = {}, Uargs(c_2) = {1, 2}, Uargs(c_3) = {},
                 Uargs(c_4) = {}
               We have the following constructor-restricted matrix interpretation:
               Interpretation Functions:
                not(x1) = [1 1 1] x1 + [0]
                          [1 1 1]      [0]
                          [1 1 1]      [0]
                or(x1, x2) = [0 0 0] x1 + [0 0 0] x2 + [0]
                             [0 0 0]      [0 0 0]      [0]
                             [0 0 0]      [0 0 0]      [0]
                and(x1, x2) = [0 0 0] x1 + [0 0 0] x2 + [0]
                              [0 0 0]      [0 0 0]      [0]
                              [0 0 0]      [0 0 0]      [0]
                not^#(x1) = [3 3 3] x1 + [0]
                            [0 0 0]      [0]
                            [0 0 0]      [0]
                c_0(x1) = [1 1 1] x1 + [0]
                          [0 0 0]      [0]
                          [0 0 0]      [0]
                c_1(x1) = [0 0 0] x1 + [0]
                          [0 0 0]      [0]
                          [0 0 0]      [0]
                and^#(x1, x2) = [0 0 0] x1 + [0 0 0] x2 + [0]
                                [0 0 0]      [0 0 0]      [0]
                                [0 0 0]      [0 0 0]      [0]
                c_2(x1, x2) = [1 0 0] x1 + [1 0 0] x2 + [0]
                              [0 1 0]      [0 1 0]      [0]
                              [0 0 1]      [0 0 1]      [0]
                c_3(x1, x2) = [0 0 0] x1 + [0 0 0] x2 + [0]
                              [0 0 0]      [0 0 0]      [0]
                              [0 0 0]      [0 0 0]      [0]
                c_4(x1, x2) = [0 0 0] x1 + [0 0 0] x2 + [0]
                              [0 0 0]      [0 0 0]      [0]
                              [0 0 0]      [0 0 0]      [0]
             
             We apply the sub-processor on the resulting sub-problem:
             
             'matrix-interpretation of dimension 3'
             --------------------------------------
             Answer:           YES(?,O(1))
             Input Problem:    DP runtime-complexity with respect to
               Strict Rules: {not^#(not(x)) -> c_0(x)}
               Weak Rules: {not^#(and(x, y)) -> c_2(not^#(x), not^#(y))}
             
             Proof Output:    
               The following argument positions are usable:
                 Uargs(not) = {}, Uargs(and) = {}, Uargs(not^#) = {},
                 Uargs(c_0) = {}, Uargs(c_2) = {1, 2}
               We have the following constructor-restricted matrix interpretation:
               Interpretation Functions:
                not(x1) = [2 2 2] x1 + [3]
                          [2 2 2]      [1]
                          [2 2 2]      [0]
                and(x1, x2) = [1 1 2] x1 + [4 4 1] x2 + [0]
                              [1 5 2]      [0 0 0]      [0]
                              [4 0 2]      [0 0 0]      [3]
                not^#(x1) = [2 2 2] x1 + [0]
                            [2 2 2]      [2]
                            [2 2 2]      [4]
                c_0(x1) = [0 0 0] x1 + [1]
                          [0 0 0]      [0]
                          [0 0 0]      [0]
                c_2(x1, x2) = [4 2 0] x1 + [1 0 0] x2 + [2]
                              [0 0 0]      [0 0 0]      [6]
                              [0 0 0]      [0 0 0]      [7]
           
           * Path {3}->{2}: inherited
             ------------------------
             
             This path is subsumed by the proof of path {3}->{2}->{5,4}.
           
           * Path {3}->{2}->{5,4}: NA
             ------------------------
             
             The usable rules for this path are:
             
               {  not(not(x)) -> x
                , not(or(x, y)) -> and(not(x), not(y))
                , not(and(x, y)) -> or(not(x), not(y))
                , and(x, or(y, z)) -> or(and(x, y), and(x, z))
                , and(or(y, z), x) -> or(and(x, y), and(x, z))}
             
             The weight gap principle does not apply:
               The input cannot be shown compatible
             Complexity induced by the adequate RMI: MAYBE
             
             We have not generated a proof for the resulting sub-problem.
    
    2) 'wdg' failed due to the following reason:
         Transformation Details:
         -----------------------
           We have computed the following set of weak (innermost) dependency pairs:
           
             {  1: not^#(not(x)) -> c_0(x)
              , 2: not^#(or(x, y)) -> c_1(and^#(not(x), not(y)))
              , 3: not^#(and(x, y)) -> c_2(not^#(x), not^#(y))
              , 4: and^#(x, or(y, z)) -> c_3(and^#(x, y), and^#(x, z))
              , 5: and^#(or(y, z), x) -> c_4(and^#(x, y), and^#(x, z))}
           
           Following Dependency Graph (modulo SCCs) was computed. (Answers to
           subproofs are indicated to the right.)
           
             ->{3}                                                       [     inherited      ]
                |
                |->{1}                                                   [    YES(?,O(1))     ]
                |
                `->{2}                                                   [     inherited      ]
                    |
                    `->{5,4}                                             [       MAYBE        ]
             
           
         
         Sub-problems:
         -------------
           * Path {3}: inherited
             -------------------
             
             This path is subsumed by the proof of path {3}->{2}->{5,4}.
           
           * Path {3}->{1}: YES(?,O(1))
             --------------------------
             
             The usable rules of this path are empty.
             
             The weightgap principle applies, using the following adequate RMI:
               The following argument positions are usable:
                 Uargs(not) = {}, Uargs(or) = {}, Uargs(and) = {},
                 Uargs(not^#) = {}, Uargs(c_0) = {}, Uargs(c_1) = {},
                 Uargs(and^#) = {}, Uargs(c_2) = {1, 2}, Uargs(c_3) = {},
                 Uargs(c_4) = {}
               We have the following constructor-restricted matrix interpretation:
               Interpretation Functions:
                not(x1) = [3 3] x1 + [0]
                          [2 1]      [0]
                or(x1, x2) = [0 0] x1 + [0 0] x2 + [0]
                             [0 0]      [0 0]      [0]
                and(x1, x2) = [0 0] x1 + [0 0] x2 + [0]
                              [0 0]      [0 0]      [0]
                not^#(x1) = [1 3] x1 + [0]
                            [0 0]      [0]
                c_0(x1) = [1 0] x1 + [0]
                          [0 0]      [0]
                c_1(x1) = [0 0] x1 + [0]
                          [0 0]      [0]
                and^#(x1, x2) = [0 0] x1 + [0 0] x2 + [0]
                                [0 0]      [0 0]      [0]
                c_2(x1, x2) = [1 0] x1 + [1 0] x2 + [0]
                              [0 1]      [0 1]      [0]
                c_3(x1, x2) = [0 0] x1 + [0 0] x2 + [0]
                              [0 0]      [0 0]      [0]
                c_4(x1, x2) = [0 0] x1 + [0 0] x2 + [0]
                              [0 0]      [0 0]      [0]
             
             We apply the sub-processor on the resulting sub-problem:
             
             'matrix-interpretation of dimension 2'
             --------------------------------------
             Answer:           YES(?,O(1))
             Input Problem:    DP runtime-complexity with respect to
               Strict Rules: {not^#(not(x)) -> c_0(x)}
               Weak Rules: {not^#(and(x, y)) -> c_2(not^#(x), not^#(y))}
             
             Proof Output:    
               The following argument positions are usable:
                 Uargs(not) = {}, Uargs(and) = {}, Uargs(not^#) = {},
                 Uargs(c_0) = {}, Uargs(c_2) = {1, 2}
               We have the following constructor-restricted matrix interpretation:
               Interpretation Functions:
                not(x1) = [2 2] x1 + [2]
                          [2 0]      [2]
                and(x1, x2) = [2 6] x1 + [2 3] x2 + [4]
                              [2 1]      [2 2]      [0]
                not^#(x1) = [2 3] x1 + [0]
                            [2 3]      [0]
                c_0(x1) = [0 0] x1 + [1]
                          [0 0]      [0]
                c_2(x1, x2) = [2 0] x1 + [1 0] x2 + [7]
                              [3 2]      [2 2]      [0]
           
           * Path {3}->{2}: inherited
             ------------------------
             
             This path is subsumed by the proof of path {3}->{2}->{5,4}.
           
           * Path {3}->{2}->{5,4}: MAYBE
             ---------------------------
             
             The usable rules for this path are:
             
               {  not(not(x)) -> x
                , not(or(x, y)) -> and(not(x), not(y))
                , not(and(x, y)) -> or(not(x), not(y))
                , and(x, or(y, z)) -> or(and(x, y), and(x, z))
                , and(or(y, z), x) -> or(and(x, y), and(x, z))}
             
             The weight gap principle does not apply:
               The input cannot be shown compatible
             Complexity induced by the adequate RMI: MAYBE
             
             We apply the sub-processor on the resulting sub-problem:
             
             'matrix-interpretation of dimension 2'
             --------------------------------------
             Answer:           MAYBE
             Input Problem:    runtime-complexity with respect to
               Rules:
                 {  not^#(or(x, y)) -> c_1(and^#(not(x), not(y)))
                  , not^#(and(x, y)) -> c_2(not^#(x), not^#(y))
                  , and^#(or(y, z), x) -> c_4(and^#(x, y), and^#(x, z))
                  , and^#(x, or(y, z)) -> c_3(and^#(x, y), and^#(x, z))
                  , not(not(x)) -> x
                  , not(or(x, y)) -> and(not(x), not(y))
                  , not(and(x, y)) -> or(not(x), not(y))
                  , and(x, or(y, z)) -> or(and(x, y), and(x, z))
                  , and(or(y, z), x) -> or(and(x, y), and(x, z))}
             
             Proof Output:    
               The input cannot be shown compatible
    
    3) 'wdg' failed due to the following reason:
         Transformation Details:
         -----------------------
           We have computed the following set of weak (innermost) dependency pairs:
           
             {  1: not^#(not(x)) -> c_0(x)
              , 2: not^#(or(x, y)) -> c_1(and^#(not(x), not(y)))
              , 3: not^#(and(x, y)) -> c_2(not^#(x), not^#(y))
              , 4: and^#(x, or(y, z)) -> c_3(and^#(x, y), and^#(x, z))
              , 5: and^#(or(y, z), x) -> c_4(and^#(x, y), and^#(x, z))}
           
           Following Dependency Graph (modulo SCCs) was computed. (Answers to
           subproofs are indicated to the right.)
           
             ->{3}                                                       [     inherited      ]
                |
                |->{1}                                                   [    YES(?,O(1))     ]
                |
                `->{2}                                                   [     inherited      ]
                    |
                    `->{5,4}                                             [       MAYBE        ]
             
           
         
         Sub-problems:
         -------------
           * Path {3}: inherited
             -------------------
             
             This path is subsumed by the proof of path {3}->{2}->{5,4}.
           
           * Path {3}->{1}: YES(?,O(1))
             --------------------------
             
             The usable rules of this path are empty.
             
             The weightgap principle applies, using the following adequate RMI:
               The following argument positions are usable:
                 Uargs(not) = {}, Uargs(or) = {}, Uargs(and) = {},
                 Uargs(not^#) = {}, Uargs(c_0) = {}, Uargs(c_1) = {},
                 Uargs(and^#) = {}, Uargs(c_2) = {1, 2}, Uargs(c_3) = {},
                 Uargs(c_4) = {}
               We have the following constructor-restricted matrix interpretation:
               Interpretation Functions:
                not(x1) = [2] x1 + [0]
                or(x1, x2) = [0] x1 + [0] x2 + [0]
                and(x1, x2) = [0] x1 + [0] x2 + [0]
                not^#(x1) = [3] x1 + [0]
                c_0(x1) = [0] x1 + [0]
                c_1(x1) = [0] x1 + [0]
                and^#(x1, x2) = [0] x1 + [0] x2 + [0]
                c_2(x1, x2) = [1] x1 + [1] x2 + [0]
                c_3(x1, x2) = [0] x1 + [0] x2 + [0]
                c_4(x1, x2) = [0] x1 + [0] x2 + [0]
             
             We apply the sub-processor on the resulting sub-problem:
             
             'matrix-interpretation of dimension 1'
             --------------------------------------
             Answer:           YES(?,O(1))
             Input Problem:    DP runtime-complexity with respect to
               Strict Rules: {not^#(not(x)) -> c_0(x)}
               Weak Rules: {not^#(and(x, y)) -> c_2(not^#(x), not^#(y))}
             
             Proof Output:    
               The following argument positions are usable:
                 Uargs(not) = {}, Uargs(and) = {}, Uargs(not^#) = {},
                 Uargs(c_0) = {}, Uargs(c_2) = {1, 2}
               We have the following constructor-restricted matrix interpretation:
               Interpretation Functions:
                not(x1) = [5] x1 + [2]
                and(x1, x2) = [2] x1 + [2] x2 + [2]
                not^#(x1) = [3] x1 + [2]
                c_0(x1) = [1] x1 + [1]
                c_2(x1, x2) = [1] x1 + [2] x2 + [2]
           
           * Path {3}->{2}: inherited
             ------------------------
             
             This path is subsumed by the proof of path {3}->{2}->{5,4}.
           
           * Path {3}->{2}->{5,4}: MAYBE
             ---------------------------
             
             The usable rules for this path are:
             
               {  not(not(x)) -> x
                , not(or(x, y)) -> and(not(x), not(y))
                , not(and(x, y)) -> or(not(x), not(y))
                , and(x, or(y, z)) -> or(and(x, y), and(x, z))
                , and(or(y, z), x) -> or(and(x, y), and(x, z))}
             
             The weight gap principle does not apply:
               The input cannot be shown compatible
             Complexity induced by the adequate RMI: MAYBE
             
             We apply the sub-processor on the resulting sub-problem:
             
             'matrix-interpretation of dimension 1'
             --------------------------------------
             Answer:           MAYBE
             Input Problem:    runtime-complexity with respect to
               Rules:
                 {  not^#(or(x, y)) -> c_1(and^#(not(x), not(y)))
                  , not^#(and(x, y)) -> c_2(not^#(x), not^#(y))
                  , and^#(or(y, z), x) -> c_4(and^#(x, y), and^#(x, z))
                  , and^#(x, or(y, z)) -> c_3(and^#(x, y), and^#(x, z))
                  , not(not(x)) -> x
                  , not(or(x, y)) -> and(not(x), not(y))
                  , not(and(x, y)) -> or(not(x), not(y))
                  , and(x, or(y, z)) -> or(and(x, y), and(x, z))
                  , and(or(y, z), x) -> or(and(x, y), and(x, z))}
             
             Proof Output:    
               The input cannot be shown compatible
    
    4) 'matrix-interpretation of dimension 1' failed due to the following reason:
         The input cannot be shown compatible
    
    5) 'Bounds with perSymbol-enrichment and initial automaton 'match'' failed due to the following reason:
         match-boundness of the problem could not be verified.
    
    6) 'Bounds with minimal-enrichment and initial automaton 'match'' failed due to the following reason:
         match-boundness of the problem could not be verified.
    

Tool pair1rc

Execution TimeUnknown
Answer
MAYBE
InputDer95 12

stdout:

MAYBE

We consider the following Problem:

  Strict Trs:
    {  not(not(x)) -> x
     , not(or(x, y)) -> and(not(x), not(y))
     , not(and(x, y)) -> or(not(x), not(y))
     , and(x, or(y, z)) -> or(and(x, y), and(x, z))
     , and(or(y, z), x) -> or(and(x, y), and(x, z))}
  StartTerms: basic terms
  Strategy: none

Certificate: MAYBE

Application of 'pair1 (timeout of 60.0 seconds)':
-------------------------------------------------
  The processor is not applicable, reason is:
   Input problem is not restricted to innermost rewriting
  
  We abort the transformation and continue with the subprocessor on the problem
  
  Strict Trs:
    {  not(not(x)) -> x
     , not(or(x, y)) -> and(not(x), not(y))
     , not(and(x, y)) -> or(not(x), not(y))
     , and(x, or(y, z)) -> or(and(x, y), and(x, z))
     , and(or(y, z), x) -> or(and(x, y), and(x, z))}
  StartTerms: basic terms
  Strategy: none
  
  1) None of the processors succeeded.
     
     Details of failed attempt(s):
     -----------------------------
       1) 'dp' failed due to the following reason:
            We have computed the following dependency pairs
            
            Strict Dependency Pairs:
              {  not^#(not(x)) -> c_1(x)
               , not^#(or(x, y)) -> c_2(and^#(not(x), not(y)))
               , not^#(and(x, y)) -> c_3(not^#(x), not^#(y))
               , and^#(x, or(y, z)) -> c_4(and^#(x, y), and^#(x, z))
               , and^#(or(y, z), x) -> c_5(and^#(x, y), and^#(x, z))}
            
            We consider the following Problem:
            
              Strict DPs:
                {  not^#(not(x)) -> c_1(x)
                 , not^#(or(x, y)) -> c_2(and^#(not(x), not(y)))
                 , not^#(and(x, y)) -> c_3(not^#(x), not^#(y))
                 , and^#(x, or(y, z)) -> c_4(and^#(x, y), and^#(x, z))
                 , and^#(or(y, z), x) -> c_5(and^#(x, y), and^#(x, z))}
              Strict Trs:
                {  not(not(x)) -> x
                 , not(or(x, y)) -> and(not(x), not(y))
                 , not(and(x, y)) -> or(not(x), not(y))
                 , and(x, or(y, z)) -> or(and(x, y), and(x, z))
                 , and(or(y, z), x) -> or(and(x, y), and(x, z))}
              StartTerms: basic terms
              Strategy: none
            
            Certificate: MAYBE
            
            Application of 'Fastest':
            -------------------------
              None of the processors succeeded.
              
              Details of failed attempt(s):
              -----------------------------
                1) 'pathanalysis' failed due to the following reason:
                     We use following congruence DG for path analysis
                     
                     ->{3}                                                       [       MAYBE        ]
                        |
                        |->{1}                                                   [         ?          ]
                        |
                        `->{2}                                                   [         ?          ]
                            |
                            `->{5,4}                                             [         ?          ]
                     
                     
                     Here rules are as follows:
                     
                       {  1: not^#(not(x)) -> c_1(x)
                        , 2: not^#(or(x, y)) -> c_2(and^#(not(x), not(y)))
                        , 3: not^#(and(x, y)) -> c_3(not^#(x), not^#(y))
                        , 4: and^#(x, or(y, z)) -> c_4(and^#(x, y), and^#(x, z))
                        , 5: and^#(or(y, z), x) -> c_5(and^#(x, y), and^#(x, z))}
                     
                     * Path {3}: MAYBE
                       ---------------
                       
                       We consider the following Problem:
                       
                         Strict DPs: {not^#(and(x, y)) -> c_3(not^#(x), not^#(y))}
                         Strict Trs:
                           {  not(not(x)) -> x
                            , not(or(x, y)) -> and(not(x), not(y))
                            , not(and(x, y)) -> or(not(x), not(y))
                            , and(x, or(y, z)) -> or(and(x, y), and(x, z))
                            , and(or(y, z), x) -> or(and(x, y), and(x, z))}
                         StartTerms: basic terms
                         Strategy: none
                       
                       Certificate: MAYBE
                       
                       Application of 'removetails >>> ... >>> ... >>> ...':
                       -----------------------------------------------------
                         The processor is inapplicable since the strict component of the
                         input problem is not empty
                         
                         We apply the transformation 'weightgap of dimension Nat 2, maximal degree 1, cbits 4 <> ...' on the resulting sub-problems:
                         Sub-problem 1:
                         --------------
                           We consider the problem
                           
                           Strict DPs: {not^#(and(x, y)) -> c_3(not^#(x), not^#(y))}
                           Strict Trs:
                             {  not(not(x)) -> x
                              , not(or(x, y)) -> and(not(x), not(y))
                              , not(and(x, y)) -> or(not(x), not(y))
                              , and(x, or(y, z)) -> or(and(x, y), and(x, z))
                              , and(or(y, z), x) -> or(and(x, y), and(x, z))}
                           StartTerms: basic terms
                           Strategy: none
                           
                           We fail transforming the problem using 'weightgap of dimension Nat 2, maximal degree 1, cbits 4'
                           
                             The weightgap principle does not apply
                           
                           We try instead 'weightgap of dimension Nat 3, maximal degree 3, cbits 4 <> ...' on the problem
                           
                           Strict DPs: {not^#(and(x, y)) -> c_3(not^#(x), not^#(y))}
                           Strict Trs:
                             {  not(not(x)) -> x
                              , not(or(x, y)) -> and(not(x), not(y))
                              , not(and(x, y)) -> or(not(x), not(y))
                              , and(x, or(y, z)) -> or(and(x, y), and(x, z))
                              , and(or(y, z), x) -> or(and(x, y), and(x, z))}
                           StartTerms: basic terms
                           Strategy: none
                           
                             We fail transforming the problem using 'weightgap of dimension Nat 3, maximal degree 3, cbits 4'
                             
                               The weightgap principle does not apply
                             
                             We try instead 'weightgap of dimension Nat 4, maximal degree 3, cbits 4' on the problem
                             
                             Strict DPs: {not^#(and(x, y)) -> c_3(not^#(x), not^#(y))}
                             Strict Trs:
                               {  not(not(x)) -> x
                                , not(or(x, y)) -> and(not(x), not(y))
                                , not(and(x, y)) -> or(not(x), not(y))
                                , and(x, or(y, z)) -> or(and(x, y), and(x, z))
                                , and(or(y, z), x) -> or(and(x, y), and(x, z))}
                             StartTerms: basic terms
                             Strategy: none
                             
                               The weightgap principle does not apply
                         
                         We abort the transformation and continue with the subprocessor on the problem
                         
                         Strict DPs: {not^#(and(x, y)) -> c_3(not^#(x), not^#(y))}
                         Strict Trs:
                           {  not(not(x)) -> x
                            , not(or(x, y)) -> and(not(x), not(y))
                            , not(and(x, y)) -> or(not(x), not(y))
                            , and(x, or(y, z)) -> or(and(x, y), and(x, z))
                            , and(or(y, z), x) -> or(and(x, y), and(x, z))}
                         StartTerms: basic terms
                         Strategy: none
                         
                         1) 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) 'matrix-interpretation of dimension 4 (timeout of 100.0 seconds)' failed due to the following reason:
                                          The input cannot be shown compatible
                                     
                                     2) 'matrix-interpretation of dimension 3 (timeout of 100.0 seconds)' failed due to the following reason:
                                          The input cannot be shown compatible
                                     
                                     3) 'matrix-interpretation of dimension 2 (timeout of 100.0 seconds)' failed due to the following reason:
                                          The input cannot be shown compatible
                                     
                              
                         
                     
                     * Path {3}->{1}: ?
                       ----------------
                       
                       CANNOT find proof of path {3}->{1}. Propably computation has been aborted since some other path cannot be solved.
                     
                     * Path {3}->{2}: ?
                       ----------------
                       
                       CANNOT find proof of path {3}->{2}. Propably computation has been aborted since some other path cannot be solved.
                     
                     * Path {3}->{2}->{5,4}: ?
                       -----------------------
                       
                       CANNOT find proof of path {3}->{2}->{5,4}. Propably computation has been aborted since some other path cannot be solved.
                
                2) 'Sequentially' 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) 'matrix-interpretation of dimension 3 (timeout of 100.0 seconds)' failed due to the following reason:
                                   The input cannot be shown compatible
                              
                              2) 'matrix-interpretation of dimension 2 (timeout of 100.0 seconds)' failed due to the following reason:
                                   The input cannot be shown compatible
                              
                       
                
       
       2) 'Fastest' failed due to the following reason:
            None of the processors succeeded.
            
            Details of failed attempt(s):
            -----------------------------
              1) 'Sequentially' 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) 'matrix-interpretation of dimension 4 (timeout of 100.0 seconds)' failed due to the following reason:
                                 The input cannot be shown compatible
                            
                            2) 'matrix-interpretation of dimension 3 (timeout of 100.0 seconds)' failed due to the following reason:
                                 The input cannot be shown compatible
                            
                            3) 'matrix-interpretation of dimension 2 (timeout of 100.0 seconds)' failed due to the following reason:
                                 The input cannot be shown compatible
                            
                     
              
              2) 'Fastest' 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..

Tool pair2rc

Execution TimeUnknown
Answer
MAYBE
InputDer95 12

stdout:

MAYBE

We consider the following Problem:

  Strict Trs:
    {  not(not(x)) -> x
     , not(or(x, y)) -> and(not(x), not(y))
     , not(and(x, y)) -> or(not(x), not(y))
     , and(x, or(y, z)) -> or(and(x, y), and(x, z))
     , and(or(y, z), x) -> or(and(x, y), and(x, z))}
  StartTerms: basic terms
  Strategy: none

Certificate: MAYBE

Application of 'pair2 (timeout of 60.0 seconds)':
-------------------------------------------------
  The processor is not applicable, reason is:
   Input problem is not restricted to innermost rewriting
  
  We abort the transformation and continue with the subprocessor on the problem
  
  Strict Trs:
    {  not(not(x)) -> x
     , not(or(x, y)) -> and(not(x), not(y))
     , not(and(x, y)) -> or(not(x), not(y))
     , and(x, or(y, z)) -> or(and(x, y), and(x, z))
     , and(or(y, z), x) -> or(and(x, y), and(x, z))}
  StartTerms: basic terms
  Strategy: none
  
  1) None of the processors succeeded.
     
     Details of failed attempt(s):
     -----------------------------
       1) 'dp' failed due to the following reason:
            We have computed the following dependency pairs
            
            Strict Dependency Pairs:
              {  not^#(not(x)) -> c_1(x)
               , not^#(or(x, y)) -> c_2(and^#(not(x), not(y)))
               , not^#(and(x, y)) -> c_3(not^#(x), not^#(y))
               , and^#(x, or(y, z)) -> c_4(and^#(x, y), and^#(x, z))
               , and^#(or(y, z), x) -> c_5(and^#(x, y), and^#(x, z))}
            
            We consider the following Problem:
            
              Strict DPs:
                {  not^#(not(x)) -> c_1(x)
                 , not^#(or(x, y)) -> c_2(and^#(not(x), not(y)))
                 , not^#(and(x, y)) -> c_3(not^#(x), not^#(y))
                 , and^#(x, or(y, z)) -> c_4(and^#(x, y), and^#(x, z))
                 , and^#(or(y, z), x) -> c_5(and^#(x, y), and^#(x, z))}
              Strict Trs:
                {  not(not(x)) -> x
                 , not(or(x, y)) -> and(not(x), not(y))
                 , not(and(x, y)) -> or(not(x), not(y))
                 , and(x, or(y, z)) -> or(and(x, y), and(x, z))
                 , and(or(y, z), x) -> or(and(x, y), and(x, z))}
              StartTerms: basic terms
              Strategy: none
            
            Certificate: MAYBE
            
            Application of 'Fastest':
            -------------------------
              None of the processors succeeded.
              
              Details of failed attempt(s):
              -----------------------------
                1) 'pathanalysis' failed due to the following reason:
                     We use following congruence DG for path analysis
                     
                     ->{3}                                                       [       MAYBE        ]
                        |
                        |->{1}                                                   [         ?          ]
                        |
                        `->{2}                                                   [         ?          ]
                            |
                            `->{5,4}                                             [         ?          ]
                     
                     
                     Here rules are as follows:
                     
                       {  1: not^#(not(x)) -> c_1(x)
                        , 2: not^#(or(x, y)) -> c_2(and^#(not(x), not(y)))
                        , 3: not^#(and(x, y)) -> c_3(not^#(x), not^#(y))
                        , 4: and^#(x, or(y, z)) -> c_4(and^#(x, y), and^#(x, z))
                        , 5: and^#(or(y, z), x) -> c_5(and^#(x, y), and^#(x, z))}
                     
                     * Path {3}: MAYBE
                       ---------------
                       
                       We consider the following Problem:
                       
                         Strict DPs: {not^#(and(x, y)) -> c_3(not^#(x), not^#(y))}
                         Strict Trs:
                           {  not(not(x)) -> x
                            , not(or(x, y)) -> and(not(x), not(y))
                            , not(and(x, y)) -> or(not(x), not(y))
                            , and(x, or(y, z)) -> or(and(x, y), and(x, z))
                            , and(or(y, z), x) -> or(and(x, y), and(x, z))}
                         StartTerms: basic terms
                         Strategy: none
                       
                       Certificate: MAYBE
                       
                       Application of 'removetails >>> ... >>> ... >>> ...':
                       -----------------------------------------------------
                         The processor is inapplicable since the strict component of the
                         input problem is not empty
                         
                         We apply the transformation 'weightgap of dimension Nat 2, maximal degree 1, cbits 4 <> ...' on the resulting sub-problems:
                         Sub-problem 1:
                         --------------
                           We consider the problem
                           
                           Strict DPs: {not^#(and(x, y)) -> c_3(not^#(x), not^#(y))}
                           Strict Trs:
                             {  not(not(x)) -> x
                              , not(or(x, y)) -> and(not(x), not(y))
                              , not(and(x, y)) -> or(not(x), not(y))
                              , and(x, or(y, z)) -> or(and(x, y), and(x, z))
                              , and(or(y, z), x) -> or(and(x, y), and(x, z))}
                           StartTerms: basic terms
                           Strategy: none
                           
                           We fail transforming the problem using 'weightgap of dimension Nat 2, maximal degree 1, cbits 4'
                           
                             The weightgap principle does not apply
                           
                           We try instead 'weightgap of dimension Nat 3, maximal degree 3, cbits 4 <> ...' on the problem
                           
                           Strict DPs: {not^#(and(x, y)) -> c_3(not^#(x), not^#(y))}
                           Strict Trs:
                             {  not(not(x)) -> x
                              , not(or(x, y)) -> and(not(x), not(y))
                              , not(and(x, y)) -> or(not(x), not(y))
                              , and(x, or(y, z)) -> or(and(x, y), and(x, z))
                              , and(or(y, z), x) -> or(and(x, y), and(x, z))}
                           StartTerms: basic terms
                           Strategy: none
                           
                             We fail transforming the problem using 'weightgap of dimension Nat 3, maximal degree 3, cbits 4'
                             
                               The weightgap principle does not apply
                             
                             We try instead 'weightgap of dimension Nat 4, maximal degree 3, cbits 4' on the problem
                             
                             Strict DPs: {not^#(and(x, y)) -> c_3(not^#(x), not^#(y))}
                             Strict Trs:
                               {  not(not(x)) -> x
                                , not(or(x, y)) -> and(not(x), not(y))
                                , not(and(x, y)) -> or(not(x), not(y))
                                , and(x, or(y, z)) -> or(and(x, y), and(x, z))
                                , and(or(y, z), x) -> or(and(x, y), and(x, z))}
                             StartTerms: basic terms
                             Strategy: none
                             
                               The weightgap principle does not apply
                         
                         We abort the transformation and continue with the subprocessor on the problem
                         
                         Strict DPs: {not^#(and(x, y)) -> c_3(not^#(x), not^#(y))}
                         Strict Trs:
                           {  not(not(x)) -> x
                            , not(or(x, y)) -> and(not(x), not(y))
                            , not(and(x, y)) -> or(not(x), not(y))
                            , and(x, or(y, z)) -> or(and(x, y), and(x, z))
                            , and(or(y, z), x) -> or(and(x, y), and(x, z))}
                         StartTerms: basic terms
                         Strategy: none
                         
                         1) None of the processors succeeded.
                            
                            Details of failed attempt(s):
                            -----------------------------
                              1) 'Sequentially' 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) 'matrix-interpretation of dimension 4 (timeout of 100.0 seconds)' failed due to the following reason:
                                                 The input cannot be shown compatible
                                            
                                            2) 'matrix-interpretation of dimension 3 (timeout of 100.0 seconds)' failed due to the following reason:
                                                 The input cannot be shown compatible
                                            
                                            3) 'matrix-interpretation of dimension 2 (timeout of 100.0 seconds)' failed due to the following reason:
                                                 The input cannot be shown compatible
                                            
                                     
                              
                              2) 'compose (statically using 'split first congruence from CWD', multiplication)' failed due to the following reason:
                                   Compose is inapplicable since some strict rule is size increasing
                                   
                                   No subproblems were generated.
                              
                         
                     
                     * Path {3}->{1}: ?
                       ----------------
                       
                       CANNOT find proof of path {3}->{1}. Propably computation has been aborted since some other path cannot be solved.
                     
                     * Path {3}->{2}: ?
                       ----------------
                       
                       CANNOT find proof of path {3}->{2}. Propably computation has been aborted since some other path cannot be solved.
                     
                     * Path {3}->{2}->{5,4}: ?
                       -----------------------
                       
                       CANNOT find proof of path {3}->{2}->{5,4}. Propably computation has been aborted since some other path cannot be solved.
                
                2) 'Sequentially' 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) 'matrix-interpretation of dimension 3 (timeout of 100.0 seconds)' failed due to the following reason:
                                   The input cannot be shown compatible
                              
                              2) 'matrix-interpretation of dimension 2 (timeout of 100.0 seconds)' failed due to the following reason:
                                   The input cannot be shown compatible
                              
                       
                
       
       2) 'Fastest' failed due to the following reason:
            None of the processors succeeded.
            
            Details of failed attempt(s):
            -----------------------------
              1) 'Sequentially' 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) 'matrix-interpretation of dimension 4 (timeout of 100.0 seconds)' failed due to the following reason:
                                 The input cannot be shown compatible
                            
                            2) 'matrix-interpretation of dimension 3 (timeout of 100.0 seconds)' failed due to the following reason:
                                 The input cannot be shown compatible
                            
                            3) 'matrix-interpretation of dimension 2 (timeout of 100.0 seconds)' failed due to the following reason:
                                 The input cannot be shown compatible
                            
                     
              
              2) 'Fastest' 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.
                     
              
       
  

Arrrr..

Tool pair3irc

Execution TimeUnknown
Answer
MAYBE
InputDer95 12

stdout:

MAYBE

We consider the following Problem:

  Strict Trs:
    {  not(not(x)) -> x
     , not(or(x, y)) -> and(not(x), not(y))
     , not(and(x, y)) -> or(not(x), not(y))
     , and(x, or(y, z)) -> or(and(x, y), and(x, z))
     , and(or(y, z), x) -> or(and(x, y), and(x, z))}
  StartTerms: basic terms
  Strategy: innermost

Certificate: MAYBE

Application of 'pair3 (timeout of 60.0 seconds)':
-------------------------------------------------
  The input problem contains no overlaps that give rise to inapplicable rules.
  
  We abort the transformation and continue with the subprocessor on the problem
  
  Strict Trs:
    {  not(not(x)) -> x
     , not(or(x, y)) -> and(not(x), not(y))
     , not(and(x, y)) -> or(not(x), not(y))
     , and(x, or(y, z)) -> or(and(x, y), and(x, z))
     , and(or(y, z), x) -> or(and(x, y), and(x, z))}
  StartTerms: basic terms
  Strategy: innermost
  
  1) None of the processors succeeded.
     
     Details of failed attempt(s):
     -----------------------------
       1) 'dp' failed due to the following reason:
            We have computed the following dependency pairs
            
            Strict Dependency Pairs:
              {  not^#(not(x)) -> c_1()
               , not^#(or(x, y)) -> c_2(and^#(not(x), not(y)))
               , not^#(and(x, y)) -> c_3(not^#(x), not^#(y))
               , and^#(x, or(y, z)) -> c_4(and^#(x, y), and^#(x, z))
               , and^#(or(y, z), x) -> c_5(and^#(x, y), and^#(x, z))}
            
            We consider the following Problem:
            
              Strict DPs:
                {  not^#(not(x)) -> c_1()
                 , not^#(or(x, y)) -> c_2(and^#(not(x), not(y)))
                 , not^#(and(x, y)) -> c_3(not^#(x), not^#(y))
                 , and^#(x, or(y, z)) -> c_4(and^#(x, y), and^#(x, z))
                 , and^#(or(y, z), x) -> c_5(and^#(x, y), and^#(x, z))}
              Strict Trs:
                {  not(not(x)) -> x
                 , not(or(x, y)) -> and(not(x), not(y))
                 , not(and(x, y)) -> or(not(x), not(y))
                 , and(x, or(y, z)) -> or(and(x, y), and(x, z))
                 , and(or(y, z), x) -> or(and(x, y), and(x, z))}
              StartTerms: basic terms
              Strategy: innermost
            
            Certificate: MAYBE
            
            Application of 'Fastest':
            -------------------------
              None of the processors succeeded.
              
              Details of failed attempt(s):
              -----------------------------
                'Sequentially' 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) 'matrix-interpretation of dimension 3 (timeout of 100.0 seconds)' failed due to the following reason:
                                The input cannot be shown compatible
                           
                           2) 'matrix-interpretation of dimension 2 (timeout of 100.0 seconds)' failed due to the following reason:
                                The input cannot be shown compatible
                           
                    
       
       2) 'Fastest' failed due to the following reason:
            None of the processors succeeded.
            
            Details of failed attempt(s):
            -----------------------------
              1) 'Sequentially' 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) 'matrix-interpretation of dimension 4 (timeout of 100.0 seconds)' failed due to the following reason:
                                 The input cannot be shown compatible
                            
                            2) 'matrix-interpretation of dimension 3 (timeout of 100.0 seconds)' failed due to the following reason:
                                 The input cannot be shown compatible
                            
                            3) 'matrix-interpretation of dimension 2 (timeout of 100.0 seconds)' failed due to the following reason:
                                 The input cannot be shown compatible
                            
                     
              
              2) 'Fastest' 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..

Tool pair3rc

Execution TimeUnknown
Answer
MAYBE
InputDer95 12

stdout:

MAYBE

We consider the following Problem:

  Strict Trs:
    {  not(not(x)) -> x
     , not(or(x, y)) -> and(not(x), not(y))
     , not(and(x, y)) -> or(not(x), not(y))
     , and(x, or(y, z)) -> or(and(x, y), and(x, z))
     , and(or(y, z), x) -> or(and(x, y), and(x, z))}
  StartTerms: basic terms
  Strategy: none

Certificate: MAYBE

Application of 'pair3 (timeout of 60.0 seconds)':
-------------------------------------------------
  The processor is not applicable, reason is:
   Input problem is not restricted to innermost rewriting
  
  We abort the transformation and continue with the subprocessor on the problem
  
  Strict Trs:
    {  not(not(x)) -> x
     , not(or(x, y)) -> and(not(x), not(y))
     , not(and(x, y)) -> or(not(x), not(y))
     , and(x, or(y, z)) -> or(and(x, y), and(x, z))
     , and(or(y, z), x) -> or(and(x, y), and(x, z))}
  StartTerms: basic terms
  Strategy: none
  
  1) None of the processors succeeded.
     
     Details of failed attempt(s):
     -----------------------------
       1) 'dp' failed due to the following reason:
            We have computed the following dependency pairs
            
            Strict Dependency Pairs:
              {  not^#(not(x)) -> c_1(x)
               , not^#(or(x, y)) -> c_2(and^#(not(x), not(y)))
               , not^#(and(x, y)) -> c_3(not^#(x), not^#(y))
               , and^#(x, or(y, z)) -> c_4(and^#(x, y), and^#(x, z))
               , and^#(or(y, z), x) -> c_5(and^#(x, y), and^#(x, z))}
            
            We consider the following Problem:
            
              Strict DPs:
                {  not^#(not(x)) -> c_1(x)
                 , not^#(or(x, y)) -> c_2(and^#(not(x), not(y)))
                 , not^#(and(x, y)) -> c_3(not^#(x), not^#(y))
                 , and^#(x, or(y, z)) -> c_4(and^#(x, y), and^#(x, z))
                 , and^#(or(y, z), x) -> c_5(and^#(x, y), and^#(x, z))}
              Strict Trs:
                {  not(not(x)) -> x
                 , not(or(x, y)) -> and(not(x), not(y))
                 , not(and(x, y)) -> or(not(x), not(y))
                 , and(x, or(y, z)) -> or(and(x, y), and(x, z))
                 , and(or(y, z), x) -> or(and(x, y), and(x, z))}
              StartTerms: basic terms
              Strategy: none
            
            Certificate: MAYBE
            
            Application of 'Fastest':
            -------------------------
              None of the processors succeeded.
              
              Details of failed attempt(s):
              -----------------------------
                'Sequentially' 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) 'matrix-interpretation of dimension 3 (timeout of 100.0 seconds)' failed due to the following reason:
                                The input cannot be shown compatible
                           
                           2) 'matrix-interpretation of dimension 2 (timeout of 100.0 seconds)' failed due to the following reason:
                                The input cannot be shown compatible
                           
                    
       
       2) 'Fastest' failed due to the following reason:
            None of the processors succeeded.
            
            Details of failed attempt(s):
            -----------------------------
              1) 'Sequentially' 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) 'matrix-interpretation of dimension 4 (timeout of 100.0 seconds)' failed due to the following reason:
                                 The input cannot be shown compatible
                            
                            2) 'matrix-interpretation of dimension 3 (timeout of 100.0 seconds)' failed due to the following reason:
                                 The input cannot be shown compatible
                            
                            3) 'matrix-interpretation of dimension 2 (timeout of 100.0 seconds)' failed due to the following reason:
                                 The input cannot be shown compatible
                            
                     
              
              2) 'Fastest' 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..

Tool rc

Execution TimeUnknown
Answer
MAYBE
InputDer95 12

stdout:

MAYBE

We consider the following Problem:

  Strict Trs:
    {  not(not(x)) -> x
     , not(or(x, y)) -> and(not(x), not(y))
     , not(and(x, y)) -> or(not(x), not(y))
     , and(x, or(y, z)) -> or(and(x, y), and(x, z))
     , and(or(y, z), x) -> or(and(x, y), and(x, z))}
  StartTerms: basic terms
  Strategy: none

Certificate: MAYBE

Application of 'rc (timeout of 60.0 seconds)':
----------------------------------------------
  None of the processors succeeded.
  
  Details of failed attempt(s):
  -----------------------------
    1) 'Fastest' failed due to the following reason:
         None of the processors succeeded.
         
         Details of failed attempt(s):
         -----------------------------
           1) 'Sequentially' 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) 'matrix-interpretation of dimension 4 (timeout of 100.0 seconds)' failed due to the following reason:
                              The input cannot be shown compatible
                         
                         2) 'matrix-interpretation of dimension 3 (timeout of 100.0 seconds)' failed due to the following reason:
                              The input cannot be shown compatible
                         
                         3) 'matrix-interpretation of dimension 2 (timeout of 100.0 seconds)' failed due to the following reason:
                              The input cannot be shown compatible
                         
                  
           
           2) 'Fastest' 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' (timeout of 5.0 seconds)' failed due to the following reason:
                       match-boundness of the problem could not be verified.
                  
                  2) 'Bounds with minimal-enrichment and initial automaton 'match' (timeout of 100.0 seconds)' failed due to the following reason:
                       match-boundness of the problem could not be verified.
                  
           
    
    2) 'dp' failed due to the following reason:
         We have computed the following dependency pairs
         
         Strict Dependency Pairs:
           {  not^#(not(x)) -> c_1(x)
            , not^#(or(x, y)) -> c_2(and^#(not(x), not(y)))
            , not^#(and(x, y)) -> c_3(not^#(x), not^#(y))
            , and^#(x, or(y, z)) -> c_4(and^#(x, y), and^#(x, z))
            , and^#(or(y, z), x) -> c_5(and^#(x, y), and^#(x, z))}
         
         We consider the following Problem:
         
           Strict DPs:
             {  not^#(not(x)) -> c_1(x)
              , not^#(or(x, y)) -> c_2(and^#(not(x), not(y)))
              , not^#(and(x, y)) -> c_3(not^#(x), not^#(y))
              , and^#(x, or(y, z)) -> c_4(and^#(x, y), and^#(x, z))
              , and^#(or(y, z), x) -> c_5(and^#(x, y), and^#(x, z))}
           Strict Trs:
             {  not(not(x)) -> x
              , not(or(x, y)) -> and(not(x), not(y))
              , not(and(x, y)) -> or(not(x), not(y))
              , and(x, or(y, z)) -> or(and(x, y), and(x, z))
              , and(or(y, z), x) -> or(and(x, y), and(x, z))}
           StartTerms: basic terms
           Strategy: none
         
         Certificate: MAYBE
         
         Application of 'usablerules':
         -----------------------------
           All rules are usable.
           
           No subproblems were generated.
    

Arrrr..

Tool tup3irc

Execution Time35.703293ms
Answer
MAYBE
InputDer95 12

stdout:

MAYBE

We consider the following Problem:

  Strict Trs:
    {  not(not(x)) -> x
     , not(or(x, y)) -> and(not(x), not(y))
     , not(and(x, y)) -> or(not(x), not(y))
     , and(x, or(y, z)) -> or(and(x, y), and(x, z))
     , and(or(y, z), x) -> or(and(x, y), and(x, z))}
  StartTerms: basic terms
  Strategy: innermost

Certificate: MAYBE

Application of 'tup3 (timeout of 60.0 seconds)':
------------------------------------------------
  The input problem contains no overlaps that give rise to inapplicable rules.
  
  We abort the transformation and continue with the subprocessor on the problem
  
  Strict Trs:
    {  not(not(x)) -> x
     , not(or(x, y)) -> and(not(x), not(y))
     , not(and(x, y)) -> or(not(x), not(y))
     , and(x, or(y, z)) -> or(and(x, y), and(x, z))
     , and(or(y, z), x) -> or(and(x, y), and(x, z))}
  StartTerms: basic terms
  Strategy: innermost
  
  1) None of the processors succeeded.
     
     Details of failed attempt(s):
     -----------------------------
       1) 'dp' failed due to the following reason:
            We have computed the following dependency pairs
            
            Strict Dependency Pairs:
              {  not^#(not(x)) -> c_1()
               , not^#(or(x, y)) -> c_2(and^#(not(x), not(y)), not^#(x), not^#(y))
               , not^#(and(x, y)) -> c_3(not^#(x), not^#(y))
               , and^#(x, or(y, z)) -> c_4(and^#(x, y), and^#(x, z))
               , and^#(or(y, z), x) -> c_5(and^#(x, y), and^#(x, z))}
            
            We consider the following Problem:
            
              Strict DPs:
                {  not^#(not(x)) -> c_1()
                 , not^#(or(x, y)) -> c_2(and^#(not(x), not(y)), not^#(x), not^#(y))
                 , not^#(and(x, y)) -> c_3(not^#(x), not^#(y))
                 , and^#(x, or(y, z)) -> c_4(and^#(x, y), and^#(x, z))
                 , and^#(or(y, z), x) -> c_5(and^#(x, y), and^#(x, z))}
              Weak Trs:
                {  not(not(x)) -> x
                 , not(or(x, y)) -> and(not(x), not(y))
                 , not(and(x, y)) -> or(not(x), not(y))
                 , and(x, or(y, z)) -> or(and(x, y), and(x, z))
                 , and(or(y, z), x) -> or(and(x, y), and(x, z))}
              StartTerms: basic terms
              Strategy: innermost
            
            Certificate: MAYBE
            
            Application of 'Fastest':
            -------------------------
              None of the processors succeeded.
              
              Details of failed attempt(s):
              -----------------------------
                'Sequentially' 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) 'matrix-interpretation of dimension 3 (timeout of 100.0 seconds)' failed due to the following reason:
                                The input cannot be shown compatible
                           
                           2) 'matrix-interpretation of dimension 2 (timeout of 100.0 seconds)' failed due to the following reason:
                                The input cannot be shown compatible
                           
                    
       
       2) 'Fastest' failed due to the following reason:
            None of the processors succeeded.
            
            Details of failed attempt(s):
            -----------------------------
              1) 'Sequentially' 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) 'matrix-interpretation of dimension 4 (timeout of 100.0 seconds)' failed due to the following reason:
                                 The input cannot be shown compatible
                            
                            2) 'matrix-interpretation of dimension 3 (timeout of 100.0 seconds)' failed due to the following reason:
                                 The input cannot be shown compatible
                            
                            3) 'matrix-interpretation of dimension 2 (timeout of 100.0 seconds)' failed due to the following reason:
                                 The input cannot be shown compatible
                            
                     
              
              2) 'Fastest' 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.
                     
              
       
  

Arrrr..