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