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