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