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