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