MAYBE
992.00/297.03	MAYBE
992.00/297.03	
992.00/297.03	We are left with following problem, upon which TcT provides the
992.00/297.03	certificate MAYBE.
992.00/297.03	
992.00/297.03	Strict Trs:
992.00/297.03	  { 0(#()) -> #()
992.00/297.03	  , +(x, #()) -> x
992.00/297.03	  , +(0(x), 0(y)) -> 0(+(x, y))
992.00/297.03	  , +(0(x), 1(y)) -> 1(+(x, y))
992.00/297.03	  , +(0(x), j(y)) -> j(+(x, y))
992.00/297.03	  , +(#(), x) -> x
992.00/297.03	  , +(+(x, y), z) -> +(x, +(y, z))
992.00/297.03	  , +(1(x), 0(y)) -> 1(+(x, y))
992.00/297.03	  , +(1(x), 1(y)) -> j(+(+(x, y), 1(#())))
992.00/297.03	  , +(1(x), j(y)) -> 0(+(x, y))
992.00/297.03	  , +(j(x), 0(y)) -> j(+(x, y))
992.00/297.03	  , +(j(x), 1(y)) -> 0(+(x, y))
992.00/297.03	  , +(j(x), j(y)) -> 1(+(+(x, y), j(#())))
992.00/297.03	  , opp(0(x)) -> 0(opp(x))
992.00/297.03	  , opp(#()) -> #()
992.00/297.03	  , opp(1(x)) -> j(opp(x))
992.00/297.03	  , opp(j(x)) -> 1(opp(x))
992.00/297.03	  , -(x, y) -> +(x, opp(y))
992.00/297.03	  , *(x, +(y, z)) -> +(*(x, y), *(x, z))
992.00/297.03	  , *(0(x), y) -> 0(*(x, y))
992.00/297.03	  , *(#(), x) -> #()
992.00/297.03	  , *(+(x, y), z) -> +(*(x, z), *(y, z))
992.00/297.03	  , *(1(x), y) -> +(0(*(x, y)), y)
992.00/297.03	  , *(j(x), y) -> -(0(*(x, y)), y)
992.00/297.03	  , *(*(x, y), z) -> *(x, *(y, z)) }
992.00/297.03	Obligation:
992.00/297.03	  innermost runtime complexity
992.00/297.03	Answer:
992.00/297.03	  MAYBE
992.00/297.03	
992.00/297.03	None of the processors succeeded.
992.00/297.03	
992.00/297.03	Details of failed attempt(s):
992.00/297.03	-----------------------------
992.00/297.03	1) 'empty' failed due to the following reason:
992.00/297.03	   
992.00/297.03	   Empty strict component of the problem is NOT empty.
992.00/297.03	
992.00/297.03	2) 'Best' failed due to the following reason:
992.00/297.03	   
992.00/297.03	   None of the processors succeeded.
992.00/297.03	   
992.00/297.03	   Details of failed attempt(s):
992.00/297.03	   -----------------------------
992.00/297.03	   1) 'With Problem ... (timeout of 297 seconds)' failed due to the
992.00/297.03	      following reason:
992.00/297.03	      
992.00/297.03	      Computation stopped due to timeout after 297.0 seconds.
992.00/297.03	   
992.00/297.03	   2) 'Best' failed due to the following reason:
992.00/297.03	      
992.00/297.03	      None of the processors succeeded.
992.00/297.03	      
992.00/297.03	      Details of failed attempt(s):
992.00/297.03	      -----------------------------
992.00/297.03	      1) 'With Problem ... (timeout of 148 seconds) (timeout of 297
992.00/297.03	         seconds)' failed due to the following reason:
992.00/297.03	         
992.00/297.03	         Computation stopped due to timeout after 148.0 seconds.
992.00/297.03	      
992.00/297.03	      2) 'Best' failed due to the following reason:
992.00/297.03	         
992.00/297.03	         None of the processors succeeded.
992.00/297.03	         
992.00/297.03	         Details of failed attempt(s):
992.00/297.03	         -----------------------------
992.00/297.03	         1) 'Polynomial Path Order (PS) (timeout of 297 seconds)' failed due
992.00/297.03	            to the following reason:
992.00/297.03	            
992.00/297.03	            The input cannot be shown compatible
992.00/297.03	         
992.00/297.03	         2) 'bsearch-popstar (timeout of 297 seconds)' failed due to the
992.00/297.03	            following reason:
992.00/297.03	            
992.00/297.03	            The input cannot be shown compatible
992.00/297.03	         
992.00/297.03	      
992.00/297.03	      3) 'Fastest (timeout of 24 seconds) (timeout of 297 seconds)'
992.00/297.03	         failed due to the following reason:
992.00/297.03	         
992.00/297.03	         None of the processors succeeded.
992.00/297.03	         
992.00/297.03	         Details of failed attempt(s):
992.00/297.03	         -----------------------------
992.00/297.03	         1) 'Bounds with minimal-enrichment and initial automaton 'match''
992.00/297.03	            failed due to the following reason:
992.00/297.03	            
992.00/297.03	            match-boundness of the problem could not be verified.
992.00/297.03	         
992.00/297.03	         2) 'Bounds with perSymbol-enrichment and initial automaton 'match''
992.00/297.03	            failed due to the following reason:
992.00/297.03	            
992.00/297.03	            match-boundness of the problem could not be verified.
992.00/297.03	         
992.00/297.03	      
992.00/297.03	   
992.00/297.03	
992.00/297.03	
992.00/297.03	Arrrr..
992.22/297.21	EOF