MAYBE
820.08/298.32	MAYBE
820.08/298.32	
820.08/298.32	We are left with following problem, upon which TcT provides the
820.08/298.32	certificate MAYBE.
820.08/298.32	
820.08/298.32	Strict Trs:
820.08/298.32	  { from(X) -> cons(X, n__from(n__s(X)))
820.08/298.32	  , from(X) -> n__from(X)
820.08/298.32	  , after(0(), XS) -> XS
820.08/298.32	  , after(s(N), cons(X, XS)) -> after(N, activate(XS))
820.08/298.32	  , s(X) -> n__s(X)
820.08/298.32	  , activate(X) -> X
820.08/298.32	  , activate(n__from(X)) -> from(activate(X))
820.08/298.32	  , activate(n__s(X)) -> s(activate(X)) }
820.08/298.32	Obligation:
820.08/298.32	  runtime complexity
820.08/298.32	Answer:
820.08/298.32	  MAYBE
820.08/298.32	
820.08/298.32	None of the processors succeeded.
820.08/298.32	
820.08/298.32	Details of failed attempt(s):
820.08/298.32	-----------------------------
820.08/298.32	1) 'With Problem ... (timeout of 297 seconds)' failed due to the
820.08/298.32	   following reason:
820.08/298.32	   
820.08/298.32	   Computation stopped due to timeout after 297.0 seconds.
820.08/298.32	
820.08/298.32	2) 'Best' failed due to the following reason:
820.08/298.32	   
820.08/298.32	   None of the processors succeeded.
820.08/298.32	   
820.08/298.32	   Details of failed attempt(s):
820.08/298.32	   -----------------------------
820.08/298.32	   1) 'With Problem ... (timeout of 148 seconds) (timeout of 297
820.08/298.32	      seconds)' failed due to the following reason:
820.08/298.32	      
820.08/298.32	      None of the processors succeeded.
820.08/298.32	      
820.08/298.32	      Details of failed attempt(s):
820.08/298.32	      -----------------------------
820.08/298.32	      1) 'empty' failed due to the following reason:
820.08/298.32	         
820.08/298.32	         Empty strict component of the problem is NOT empty.
820.08/298.32	      
820.08/298.32	      2) 'With Problem ...' failed due to the following reason:
820.08/298.32	         
820.08/298.32	         None of the processors succeeded.
820.08/298.32	         
820.08/298.32	         Details of failed attempt(s):
820.08/298.32	         -----------------------------
820.08/298.32	         1) 'empty' failed due to the following reason:
820.08/298.32	            
820.08/298.32	            Empty strict component of the problem is NOT empty.
820.08/298.32	         
820.08/298.32	         2) 'Fastest' failed due to the following reason:
820.08/298.32	            
820.08/298.32	            None of the processors succeeded.
820.08/298.32	            
820.08/298.32	            Details of failed attempt(s):
820.08/298.32	            -----------------------------
820.08/298.32	            1) 'With Problem ...' failed due to the following reason:
820.08/298.32	               
820.08/298.32	               None of the processors succeeded.
820.08/298.32	               
820.08/298.32	               Details of failed attempt(s):
820.08/298.32	               -----------------------------
820.08/298.32	               1) 'empty' failed due to the following reason:
820.08/298.32	                  
820.08/298.32	                  Empty strict component of the problem is NOT empty.
820.08/298.32	               
820.08/298.32	               2) 'With Problem ...' failed due to the following reason:
820.08/298.32	                  
820.08/298.32	                  None of the processors succeeded.
820.08/298.32	                  
820.08/298.32	                  Details of failed attempt(s):
820.08/298.32	                  -----------------------------
820.08/298.32	                  1) 'empty' failed due to the following reason:
820.08/298.32	                     
820.08/298.32	                     Empty strict component of the problem is NOT empty.
820.08/298.32	                  
820.08/298.32	                  2) 'With Problem ...' failed due to the following reason:
820.08/298.32	                     
820.08/298.32	                     None of the processors succeeded.
820.08/298.32	                     
820.08/298.32	                     Details of failed attempt(s):
820.08/298.32	                     -----------------------------
820.08/298.32	                     1) 'empty' failed due to the following reason:
820.08/298.32	                        
820.08/298.32	                        Empty strict component of the problem is NOT empty.
820.08/298.32	                     
820.08/298.32	                     2) 'With Problem ...' failed due to the following reason:
820.08/298.32	                        
820.08/298.32	                        Empty strict component of the problem is NOT empty.
820.08/298.32	                     
820.08/298.32	                  
820.08/298.32	               
820.08/298.32	            
820.08/298.32	            2) 'With Problem ...' failed due to the following reason:
820.08/298.32	               
820.08/298.32	               None of the processors succeeded.
820.08/298.32	               
820.08/298.32	               Details of failed attempt(s):
820.08/298.32	               -----------------------------
820.08/298.32	               1) 'empty' failed due to the following reason:
820.08/298.32	                  
820.08/298.32	                  Empty strict component of the problem is NOT empty.
820.08/298.32	               
820.08/298.32	               2) 'With Problem ...' failed due to the following reason:
820.08/298.32	                  
820.08/298.32	                  Empty strict component of the problem is NOT empty.
820.08/298.32	               
820.08/298.32	            
820.08/298.32	         
820.08/298.32	      
820.08/298.32	   
820.08/298.32	   2) 'Best' failed due to the following reason:
820.08/298.32	      
820.08/298.32	      None of the processors succeeded.
820.08/298.32	      
820.08/298.32	      Details of failed attempt(s):
820.08/298.32	      -----------------------------
820.08/298.32	      1) 'Polynomial Path Order (PS) (timeout of 297 seconds)' failed due
820.08/298.32	         to the following reason:
820.08/298.32	         
820.08/298.32	         The processor is inapplicable, reason:
820.08/298.32	           Processor only applicable for innermost runtime complexity analysis
820.08/298.32	      
820.08/298.32	      2) 'bsearch-popstar (timeout of 297 seconds)' failed due to the
820.08/298.32	         following reason:
820.08/298.32	         
820.08/298.32	         The processor is inapplicable, reason:
820.08/298.32	           Processor only applicable for innermost runtime complexity analysis
820.08/298.32	      
820.08/298.32	   
820.08/298.32	   3) 'Fastest (timeout of 24 seconds) (timeout of 297 seconds)'
820.08/298.32	      failed due to the following reason:
820.08/298.32	      
820.08/298.32	      None of the processors succeeded.
820.08/298.32	      
820.08/298.32	      Details of failed attempt(s):
820.08/298.32	      -----------------------------
820.08/298.32	      1) 'Bounds with minimal-enrichment and initial automaton 'match''
820.08/298.32	         failed due to the following reason:
820.08/298.32	         
820.08/298.32	         match-boundness of the problem could not be verified.
820.08/298.32	      
820.08/298.32	      2) 'Bounds with perSymbol-enrichment and initial automaton 'match''
820.08/298.32	         failed due to the following reason:
820.08/298.32	         
820.08/298.32	         match-boundness of the problem could not be verified.
820.08/298.32	      
820.08/298.32	   
820.08/298.32	
820.08/298.32	3) 'Weak Dependency Pairs (timeout of 297 seconds)' failed due to
820.08/298.32	   the following reason:
820.08/298.32	   
820.08/298.32	   We add the following weak dependency pairs:
820.08/298.32	   
820.08/298.32	   Strict DPs:
820.08/298.32	     { from^#(X) -> c_1(X, X)
820.08/298.32	     , from^#(X) -> c_2(X)
820.08/298.32	     , after^#(0(), XS) -> c_3(XS)
820.08/298.32	     , after^#(s(N), cons(X, XS)) -> c_4(after^#(N, activate(XS)))
820.08/298.32	     , s^#(X) -> c_5(X)
820.08/298.32	     , activate^#(X) -> c_6(X)
820.08/298.32	     , activate^#(n__from(X)) -> c_7(from^#(activate(X)))
820.08/298.32	     , activate^#(n__s(X)) -> c_8(s^#(activate(X))) }
820.08/298.32	   
820.08/298.32	   and mark the set of starting terms.
820.08/298.32	   
820.08/298.32	   We are left with following problem, upon which TcT provides the
820.08/298.32	   certificate MAYBE.
820.08/298.32	   
820.08/298.32	   Strict DPs:
820.08/298.32	     { from^#(X) -> c_1(X, X)
820.08/298.32	     , from^#(X) -> c_2(X)
820.08/298.32	     , after^#(0(), XS) -> c_3(XS)
820.08/298.32	     , after^#(s(N), cons(X, XS)) -> c_4(after^#(N, activate(XS)))
820.08/298.32	     , s^#(X) -> c_5(X)
820.08/298.32	     , activate^#(X) -> c_6(X)
820.08/298.32	     , activate^#(n__from(X)) -> c_7(from^#(activate(X)))
820.08/298.32	     , activate^#(n__s(X)) -> c_8(s^#(activate(X))) }
820.08/298.32	   Strict Trs:
820.08/298.32	     { from(X) -> cons(X, n__from(n__s(X)))
820.08/298.32	     , from(X) -> n__from(X)
820.08/298.32	     , after(0(), XS) -> XS
820.08/298.32	     , after(s(N), cons(X, XS)) -> after(N, activate(XS))
820.08/298.32	     , s(X) -> n__s(X)
820.08/298.32	     , activate(X) -> X
820.08/298.32	     , activate(n__from(X)) -> from(activate(X))
820.08/298.32	     , activate(n__s(X)) -> s(activate(X)) }
820.08/298.32	   Obligation:
820.08/298.32	     runtime complexity
820.08/298.32	   Answer:
820.08/298.32	     MAYBE
820.08/298.32	   
820.08/298.32	   Empty strict component of the problem is NOT empty.
820.08/298.32	
820.08/298.32	
820.08/298.32	Arrrr..
820.34/298.56	EOF