MAYBE
143.12/69.85	MAYBE
143.12/69.85	
143.12/69.85	We are left with following problem, upon which TcT provides the
143.12/69.85	certificate MAYBE.
143.12/69.85	
143.12/69.85	Strict Trs:
143.12/69.85	  { cond(true(), x, y) -> cond(gr(x, y), x, add(x, y))
143.12/69.85	  , gr(0(), x) -> false()
143.12/69.85	  , gr(s(x), 0()) -> true()
143.12/69.85	  , gr(s(x), s(y)) -> gr(x, y)
143.12/69.85	  , add(0(), x) -> x
143.12/69.85	  , add(s(x), y) -> s(add(x, y)) }
143.12/69.85	Obligation:
143.12/69.85	  runtime complexity
143.12/69.85	Answer:
143.12/69.85	  MAYBE
143.12/69.85	
143.12/69.85	None of the processors succeeded.
143.12/69.85	
143.12/69.85	Details of failed attempt(s):
143.12/69.85	-----------------------------
143.12/69.85	1) 'Best' failed due to the following reason:
143.12/69.85	   
143.12/69.85	   None of the processors succeeded.
143.12/69.85	   
143.12/69.85	   Details of failed attempt(s):
143.12/69.85	   -----------------------------
143.12/69.85	   1) 'With Problem ... (timeout of 148 seconds) (timeout of 297
143.12/69.85	      seconds)' failed due to the following reason:
143.12/69.85	      
143.12/69.85	      None of the processors succeeded.
143.12/69.85	      
143.12/69.85	      Details of failed attempt(s):
143.12/69.85	      -----------------------------
143.12/69.85	      1) 'empty' failed due to the following reason:
143.12/69.85	         
143.12/69.85	         Empty strict component of the problem is NOT empty.
143.12/69.85	      
143.12/69.85	      2) 'With Problem ...' failed due to the following reason:
143.12/69.85	         
143.12/69.85	         None of the processors succeeded.
143.12/69.85	         
143.12/69.85	         Details of failed attempt(s):
143.12/69.85	         -----------------------------
143.12/69.85	         1) 'empty' failed due to the following reason:
143.12/69.85	            
143.12/69.85	            Empty strict component of the problem is NOT empty.
143.12/69.85	         
143.12/69.85	         2) 'Fastest' failed due to the following reason:
143.12/69.85	            
143.12/69.85	            None of the processors succeeded.
143.12/69.85	            
143.12/69.85	            Details of failed attempt(s):
143.12/69.85	            -----------------------------
143.12/69.85	            1) 'With Problem ...' failed due to the following reason:
143.12/69.85	               
143.12/69.85	               None of the processors succeeded.
143.12/69.85	               
143.12/69.85	               Details of failed attempt(s):
143.12/69.85	               -----------------------------
143.12/69.85	               1) 'empty' failed due to the following reason:
143.12/69.85	                  
143.12/69.85	                  Empty strict component of the problem is NOT empty.
143.12/69.85	               
143.12/69.85	               2) 'With Problem ...' failed due to the following reason:
143.12/69.85	                  
143.12/69.85	                  Empty strict component of the problem is NOT empty.
143.12/69.85	               
143.12/69.85	            
143.12/69.85	            2) 'With Problem ...' failed due to the following reason:
143.12/69.85	               
143.12/69.85	               None of the processors succeeded.
143.12/69.85	               
143.12/69.85	               Details of failed attempt(s):
143.12/69.85	               -----------------------------
143.12/69.85	               1) 'empty' failed due to the following reason:
143.12/69.85	                  
143.12/69.85	                  Empty strict component of the problem is NOT empty.
143.12/69.85	               
143.12/69.85	               2) 'With Problem ...' failed due to the following reason:
143.12/69.85	                  
143.12/69.85	                  None of the processors succeeded.
143.12/69.85	                  
143.12/69.85	                  Details of failed attempt(s):
143.12/69.85	                  -----------------------------
143.12/69.85	                  1) 'empty' failed due to the following reason:
143.12/69.85	                     
143.12/69.85	                     Empty strict component of the problem is NOT empty.
143.12/69.85	                  
143.12/69.85	                  2) 'With Problem ...' failed due to the following reason:
143.12/69.85	                     
143.12/69.85	                     None of the processors succeeded.
143.12/69.85	                     
143.12/69.85	                     Details of failed attempt(s):
143.12/69.85	                     -----------------------------
143.12/69.85	                     1) 'empty' failed due to the following reason:
143.12/69.85	                        
143.12/69.85	                        Empty strict component of the problem is NOT empty.
143.12/69.85	                     
143.12/69.85	                     2) 'With Problem ...' failed due to the following reason:
143.12/69.85	                        
143.12/69.85	                        Empty strict component of the problem is NOT empty.
143.12/69.85	                     
143.12/69.85	                  
143.12/69.85	               
143.12/69.85	            
143.12/69.85	         
143.12/69.85	      
143.12/69.85	   
143.12/69.85	   2) 'Fastest (timeout of 24 seconds) (timeout of 297 seconds)'
143.12/69.85	      failed due to the following reason:
143.12/69.85	      
143.12/69.85	      None of the processors succeeded.
143.12/69.85	      
143.12/69.85	      Details of failed attempt(s):
143.12/69.85	      -----------------------------
143.12/69.85	      1) 'Bounds with perSymbol-enrichment and initial automaton 'match''
143.12/69.85	         failed due to the following reason:
143.12/69.85	         
143.12/69.85	         match-boundness of the problem could not be verified.
143.12/69.85	      
143.12/69.85	      2) 'Bounds with minimal-enrichment and initial automaton 'match''
143.12/69.85	         failed due to the following reason:
143.12/69.85	         
143.12/69.85	         match-boundness of the problem could not be verified.
143.12/69.85	      
143.12/69.85	   
143.12/69.85	   3) 'Best' failed due to the following reason:
143.12/69.85	      
143.12/69.85	      None of the processors succeeded.
143.12/69.85	      
143.12/69.85	      Details of failed attempt(s):
143.12/69.85	      -----------------------------
143.12/69.85	      1) 'Polynomial Path Order (PS) (timeout of 297 seconds)' failed due
143.12/69.85	         to the following reason:
143.12/69.85	         
143.12/69.85	         The processor is inapplicable, reason:
143.12/69.85	           Processor only applicable for innermost runtime complexity analysis
143.12/69.85	      
143.12/69.85	      2) 'bsearch-popstar (timeout of 297 seconds)' failed due to the
143.12/69.85	         following reason:
143.12/69.85	         
143.12/69.85	         The processor is inapplicable, reason:
143.12/69.85	           Processor only applicable for innermost runtime complexity analysis
143.12/69.85	      
143.12/69.85	   
143.12/69.85	
143.12/69.85	2) 'Weak Dependency Pairs (timeout of 297 seconds)' failed due to
143.12/69.85	   the following reason:
143.12/69.85	   
143.12/69.85	   We add the following weak dependency pairs:
143.12/69.85	   
143.12/69.85	   Strict DPs:
143.12/69.85	     { cond^#(true(), x, y) -> c_1(cond^#(gr(x, y), x, add(x, y)))
143.12/69.85	     , gr^#(0(), x) -> c_2()
143.12/69.85	     , gr^#(s(x), 0()) -> c_3()
143.12/69.85	     , gr^#(s(x), s(y)) -> c_4(gr^#(x, y))
143.12/69.85	     , add^#(0(), x) -> c_5(x)
143.12/69.85	     , add^#(s(x), y) -> c_6(add^#(x, y)) }
143.12/69.85	   
143.12/69.85	   and mark the set of starting terms.
143.12/69.85	   
143.12/69.85	   We are left with following problem, upon which TcT provides the
143.12/69.85	   certificate MAYBE.
143.12/69.85	   
143.12/69.85	   Strict DPs:
143.12/69.85	     { cond^#(true(), x, y) -> c_1(cond^#(gr(x, y), x, add(x, y)))
143.12/69.85	     , gr^#(0(), x) -> c_2()
143.12/69.85	     , gr^#(s(x), 0()) -> c_3()
143.12/69.85	     , gr^#(s(x), s(y)) -> c_4(gr^#(x, y))
143.12/69.85	     , add^#(0(), x) -> c_5(x)
143.12/69.85	     , add^#(s(x), y) -> c_6(add^#(x, y)) }
143.12/69.85	   Strict Trs:
143.12/69.85	     { cond(true(), x, y) -> cond(gr(x, y), x, add(x, y))
143.12/69.85	     , gr(0(), x) -> false()
143.12/69.85	     , gr(s(x), 0()) -> true()
143.12/69.85	     , gr(s(x), s(y)) -> gr(x, y)
143.12/69.85	     , add(0(), x) -> x
143.12/69.85	     , add(s(x), y) -> s(add(x, y)) }
143.12/69.85	   Obligation:
143.12/69.85	     runtime complexity
143.12/69.85	   Answer:
143.12/69.85	     MAYBE
143.12/69.85	   
143.12/69.85	   We estimate the number of application of {2,3} by applications of
143.12/69.85	   Pre({2,3}) = {4,5}. Here rules are labeled as follows:
143.12/69.85	   
143.12/69.85	     DPs:
143.12/69.85	       { 1: cond^#(true(), x, y) -> c_1(cond^#(gr(x, y), x, add(x, y)))
143.12/69.85	       , 2: gr^#(0(), x) -> c_2()
143.12/69.85	       , 3: gr^#(s(x), 0()) -> c_3()
143.12/69.85	       , 4: gr^#(s(x), s(y)) -> c_4(gr^#(x, y))
143.12/69.85	       , 5: add^#(0(), x) -> c_5(x)
143.12/69.85	       , 6: add^#(s(x), y) -> c_6(add^#(x, y)) }
143.12/69.85	   
143.12/69.85	   We are left with following problem, upon which TcT provides the
143.12/69.85	   certificate MAYBE.
143.12/69.85	   
143.12/69.85	   Strict DPs:
143.12/69.85	     { cond^#(true(), x, y) -> c_1(cond^#(gr(x, y), x, add(x, y)))
143.12/69.85	     , gr^#(s(x), s(y)) -> c_4(gr^#(x, y))
143.12/69.85	     , add^#(0(), x) -> c_5(x)
143.12/69.85	     , add^#(s(x), y) -> c_6(add^#(x, y)) }
143.12/69.85	   Strict Trs:
143.12/69.85	     { cond(true(), x, y) -> cond(gr(x, y), x, add(x, y))
143.12/69.85	     , gr(0(), x) -> false()
143.12/69.85	     , gr(s(x), 0()) -> true()
143.12/69.85	     , gr(s(x), s(y)) -> gr(x, y)
143.12/69.85	     , add(0(), x) -> x
143.12/69.85	     , add(s(x), y) -> s(add(x, y)) }
143.12/69.85	   Weak DPs:
143.12/69.85	     { gr^#(0(), x) -> c_2()
143.12/69.85	     , gr^#(s(x), 0()) -> c_3() }
143.12/69.85	   Obligation:
143.12/69.85	     runtime complexity
143.12/69.85	   Answer:
143.12/69.85	     MAYBE
143.12/69.85	   
143.12/69.85	   Empty strict component of the problem is NOT empty.
143.12/69.85	
143.12/69.85	
143.12/69.85	Arrrr..
143.26/69.97	EOF