MAYBE
969.03/297.03	MAYBE
969.03/297.03	
969.03/297.03	We are left with following problem, upon which TcT provides the
969.03/297.03	certificate MAYBE.
969.03/297.03	
969.03/297.03	Strict Trs:
969.03/297.03	  { app(x, y) -> helpa(0(), plus(length(x), length(y)), x, y)
969.03/297.03	  , helpa(c, l, ys, zs) -> if(ge(c, l), c, l, ys, zs)
969.03/297.03	  , plus(x, 0()) -> x
969.03/297.03	  , plus(x, s(y)) -> s(plus(x, y))
969.03/297.03	  , length(nil()) -> 0()
969.03/297.03	  , length(cons(x, y)) -> s(length(y))
969.03/297.03	  , if(true(), c, l, ys, zs) -> nil()
969.03/297.03	  , if(false(), c, l, ys, zs) -> helpb(c, l, ys, zs)
969.03/297.03	  , ge(x, 0()) -> true()
969.03/297.03	  , ge(0(), s(x)) -> false()
969.03/297.03	  , ge(s(x), s(y)) -> ge(x, y)
969.03/297.03	  , helpb(c, l, ys, zs) ->
969.03/297.03	    cons(take(c, ys, zs), helpa(s(c), l, ys, zs))
969.03/297.03	  , take(0(), nil(), cons(y, ys)) -> y
969.03/297.03	  , take(0(), cons(x, xs()), ys) -> x
969.03/297.03	  , take(s(c), nil(), cons(y, ys)) -> take(c, nil(), ys)
969.03/297.03	  , take(s(c), cons(x, xs()), ys) -> take(c, xs(), ys) }
969.03/297.03	Obligation:
969.03/297.03	  innermost runtime complexity
969.03/297.03	Answer:
969.03/297.03	  MAYBE
969.03/297.03	
969.03/297.03	None of the processors succeeded.
969.03/297.03	
969.03/297.03	Details of failed attempt(s):
969.03/297.03	-----------------------------
969.03/297.03	1) 'empty' failed due to the following reason:
969.03/297.03	   
969.03/297.03	   Empty strict component of the problem is NOT empty.
969.03/297.03	
969.03/297.03	2) 'Best' failed due to the following reason:
969.03/297.03	   
969.03/297.03	   None of the processors succeeded.
969.03/297.03	   
969.03/297.03	   Details of failed attempt(s):
969.03/297.03	   -----------------------------
969.03/297.03	   1) 'With Problem ... (timeout of 297 seconds)' failed due to the
969.03/297.03	      following reason:
969.03/297.03	      
969.03/297.03	      Computation stopped due to timeout after 297.0 seconds.
969.03/297.03	   
969.03/297.03	   2) 'Best' failed due to the following reason:
969.03/297.03	      
969.03/297.03	      None of the processors succeeded.
969.03/297.03	      
969.03/297.03	      Details of failed attempt(s):
969.03/297.03	      -----------------------------
969.03/297.03	      1) 'With Problem ... (timeout of 148 seconds) (timeout of 297
969.03/297.03	         seconds)' failed due to the following reason:
969.03/297.03	         
969.03/297.03	         Computation stopped due to timeout after 148.0 seconds.
969.03/297.03	      
969.03/297.03	      2) 'Best' failed due to the following reason:
969.03/297.03	         
969.03/297.03	         None of the processors succeeded.
969.03/297.03	         
969.03/297.03	         Details of failed attempt(s):
969.03/297.03	         -----------------------------
969.03/297.03	         1) 'bsearch-popstar (timeout of 297 seconds)' failed due to the
969.03/297.03	            following reason:
969.03/297.03	            
969.03/297.03	            The input cannot be shown compatible
969.03/297.03	         
969.03/297.03	         2) 'Polynomial Path Order (PS) (timeout of 297 seconds)' failed due
969.03/297.03	            to the following reason:
969.03/297.03	            
969.03/297.03	            The input cannot be shown compatible
969.03/297.03	         
969.03/297.03	      
969.03/297.03	      3) 'Fastest (timeout of 24 seconds) (timeout of 297 seconds)'
969.03/297.03	         failed due to the following reason:
969.03/297.03	         
969.03/297.03	         None of the processors succeeded.
969.03/297.03	         
969.03/297.03	         Details of failed attempt(s):
969.03/297.03	         -----------------------------
969.03/297.03	         1) 'Bounds with minimal-enrichment and initial automaton 'match''
969.03/297.03	            failed due to the following reason:
969.03/297.03	            
969.03/297.03	            match-boundness of the problem could not be verified.
969.03/297.03	         
969.03/297.03	         2) 'Bounds with perSymbol-enrichment and initial automaton 'match''
969.03/297.03	            failed due to the following reason:
969.03/297.03	            
969.03/297.03	            match-boundness of the problem could not be verified.
969.03/297.03	         
969.03/297.03	      
969.03/297.03	   
969.03/297.03	
969.03/297.03	
969.03/297.03	Arrrr..
969.47/297.43	EOF