MAYBE
969.01/297.01	MAYBE
969.01/297.01	
969.01/297.01	We are left with following problem, upon which TcT provides the
969.01/297.01	certificate MAYBE.
969.01/297.01	
969.01/297.01	Strict Trs:
969.01/297.01	  { fib(N) -> sel(N, fib1(s(0()), s(0())))
969.01/297.01	  , sel(s(N), cons(X, XS)) -> sel(N, activate(XS))
969.01/297.01	  , sel(0(), cons(X, XS)) -> X
969.01/297.01	  , fib1(X, Y) -> cons(X, n__fib1(Y, n__add(X, Y)))
969.01/297.01	  , fib1(X1, X2) -> n__fib1(X1, X2)
969.01/297.01	  , add(X1, X2) -> n__add(X1, X2)
969.01/297.01	  , add(s(X), Y) -> s(add(X, Y))
969.01/297.01	  , add(0(), X) -> X
969.01/297.01	  , activate(X) -> X
969.01/297.01	  , activate(n__fib1(X1, X2)) -> fib1(activate(X1), activate(X2))
969.01/297.01	  , activate(n__add(X1, X2)) -> add(activate(X1), activate(X2)) }
969.01/297.01	Obligation:
969.01/297.01	  innermost runtime complexity
969.01/297.01	Answer:
969.01/297.01	  MAYBE
969.01/297.01	
969.01/297.01	None of the processors succeeded.
969.01/297.01	
969.01/297.01	Details of failed attempt(s):
969.01/297.01	-----------------------------
969.01/297.01	1) 'empty' failed due to the following reason:
969.01/297.01	   
969.01/297.01	   Empty strict component of the problem is NOT empty.
969.01/297.01	
969.01/297.01	2) 'Best' failed due to the following reason:
969.01/297.01	   
969.01/297.01	   None of the processors succeeded.
969.01/297.01	   
969.01/297.01	   Details of failed attempt(s):
969.01/297.01	   -----------------------------
969.01/297.01	   1) 'With Problem ... (timeout of 297 seconds)' failed due to the
969.01/297.02	      following reason:
969.01/297.02	      
969.01/297.02	      Computation stopped due to timeout after 297.0 seconds.
969.01/297.02	   
969.01/297.02	   2) 'Best' failed due to the following reason:
969.01/297.02	      
969.01/297.02	      None of the processors succeeded.
969.01/297.02	      
969.01/297.02	      Details of failed attempt(s):
969.01/297.02	      -----------------------------
969.01/297.02	      1) 'With Problem ... (timeout of 148 seconds) (timeout of 297
969.01/297.02	         seconds)' failed due to the following reason:
969.01/297.02	         
969.01/297.02	         Computation stopped due to timeout after 148.0 seconds.
969.01/297.02	      
969.01/297.02	      2) 'Best' failed due to the following reason:
969.01/297.02	         
969.01/297.02	         None of the processors succeeded.
969.01/297.02	         
969.01/297.02	         Details of failed attempt(s):
969.01/297.02	         -----------------------------
969.01/297.02	         1) 'bsearch-popstar (timeout of 297 seconds)' failed due to the
969.01/297.02	            following reason:
969.01/297.02	            
969.01/297.02	            The input cannot be shown compatible
969.01/297.02	         
969.01/297.02	         2) 'Polynomial Path Order (PS) (timeout of 297 seconds)' failed due
969.01/297.02	            to the following reason:
969.01/297.02	            
969.01/297.02	            The input cannot be shown compatible
969.01/297.02	         
969.01/297.02	      
969.01/297.02	      3) 'Fastest (timeout of 24 seconds) (timeout of 297 seconds)'
969.01/297.02	         failed due to the following reason:
969.01/297.02	         
969.01/297.02	         None of the processors succeeded.
969.01/297.02	         
969.01/297.02	         Details of failed attempt(s):
969.01/297.02	         -----------------------------
969.01/297.02	         1) 'Bounds with minimal-enrichment and initial automaton 'match''
969.01/297.02	            failed due to the following reason:
969.01/297.02	            
969.01/297.02	            match-boundness of the problem could not be verified.
969.01/297.02	         
969.01/297.02	         2) 'Bounds with perSymbol-enrichment and initial automaton 'match''
969.01/297.02	            failed due to the following reason:
969.01/297.02	            
969.01/297.02	            match-boundness of the problem could not be verified.
969.01/297.02	         
969.01/297.02	      
969.01/297.02	   
969.01/297.02	
969.01/297.02	
969.01/297.02	Arrrr..
969.42/297.43	EOF