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