MAYBE
953.80/297.02	MAYBE
953.80/297.02	
953.80/297.02	We are left with following problem, upon which TcT provides the
953.80/297.02	certificate MAYBE.
953.80/297.02	
953.80/297.02	Strict Trs:
953.80/297.02	  { a__nats() -> cons(0(), incr(nats()))
953.80/297.02	  , a__nats() -> nats()
953.80/297.02	  , a__pairs() -> cons(0(), incr(odds()))
953.80/297.02	  , a__pairs() -> pairs()
953.80/297.02	  , a__odds() -> odds()
953.80/297.02	  , a__odds() -> a__incr(a__pairs())
953.80/297.02	  , a__incr(X) -> incr(X)
953.80/297.02	  , a__incr(cons(X, XS)) -> cons(s(mark(X)), incr(XS))
953.80/297.02	  , mark(cons(X1, X2)) -> cons(mark(X1), X2)
953.80/297.02	  , mark(0()) -> 0()
953.80/297.02	  , mark(incr(X)) -> a__incr(mark(X))
953.80/297.02	  , mark(nats()) -> a__nats()
953.80/297.02	  , mark(odds()) -> a__odds()
953.80/297.02	  , mark(s(X)) -> s(mark(X))
953.80/297.02	  , mark(pairs()) -> a__pairs()
953.80/297.02	  , mark(head(X)) -> a__head(mark(X))
953.80/297.02	  , mark(tail(X)) -> a__tail(mark(X))
953.80/297.02	  , mark(nil()) -> nil()
953.80/297.02	  , a__head(X) -> head(X)
953.80/297.02	  , a__head(cons(X, XS)) -> mark(X)
953.80/297.02	  , a__tail(X) -> tail(X)
953.80/297.02	  , a__tail(cons(X, XS)) -> mark(XS) }
953.80/297.02	Obligation:
953.80/297.02	  innermost runtime complexity
953.80/297.02	Answer:
953.80/297.02	  MAYBE
953.80/297.02	
953.80/297.02	None of the processors succeeded.
953.80/297.02	
953.80/297.02	Details of failed attempt(s):
953.80/297.02	-----------------------------
953.80/297.02	1) 'empty' failed due to the following reason:
953.80/297.02	   
953.80/297.02	   Empty strict component of the problem is NOT empty.
953.80/297.02	
953.80/297.02	2) 'Best' failed due to the following reason:
953.80/297.02	   
953.80/297.02	   None of the processors succeeded.
953.80/297.02	   
953.80/297.02	   Details of failed attempt(s):
953.80/297.02	   -----------------------------
953.80/297.02	   1) 'With Problem ... (timeout of 297 seconds)' failed due to the
953.80/297.02	      following reason:
953.80/297.02	      
953.80/297.02	      Computation stopped due to timeout after 297.0 seconds.
953.80/297.02	   
953.80/297.02	   2) 'Best' failed due to the following reason:
953.80/297.02	      
953.80/297.02	      None of the processors succeeded.
953.80/297.02	      
953.80/297.02	      Details of failed attempt(s):
953.80/297.02	      -----------------------------
953.80/297.02	      1) 'With Problem ... (timeout of 148 seconds) (timeout of 297
953.80/297.02	         seconds)' failed due to the following reason:
953.80/297.02	         
953.80/297.02	         Computation stopped due to timeout after 148.0 seconds.
953.80/297.02	      
953.80/297.02	      2) 'Fastest (timeout of 24 seconds) (timeout of 297 seconds)'
953.80/297.02	         failed due to the following reason:
953.80/297.02	         
953.80/297.02	         Computation stopped due to timeout after 24.0 seconds.
953.80/297.02	      
953.80/297.02	      3) 'Best' failed due to the following reason:
953.80/297.02	         
953.80/297.02	         None of the processors succeeded.
953.80/297.02	         
953.80/297.02	         Details of failed attempt(s):
953.80/297.02	         -----------------------------
953.80/297.02	         1) 'bsearch-popstar (timeout of 297 seconds)' failed due to the
953.80/297.02	            following reason:
953.80/297.02	            
953.80/297.02	            The input cannot be shown compatible
953.80/297.02	         
953.80/297.02	         2) 'Polynomial Path Order (PS) (timeout of 297 seconds)' failed due
953.80/297.02	            to the following reason:
953.80/297.02	            
953.80/297.02	            The input cannot be shown compatible
953.80/297.02	         
953.80/297.02	      
953.80/297.02	   
953.80/297.02	
953.80/297.02	
953.80/297.02	Arrrr..
953.93/297.15	EOF