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