MAYBE
677.80/297.12	MAYBE
677.80/297.12	
677.80/297.12	We are left with following problem, upon which TcT provides the
677.80/297.12	certificate MAYBE.
677.80/297.12	
677.80/297.12	Strict Trs:
677.80/297.12	  { f(node(s(n), xs)) -> f(addchild(select(xs), node(n, xs)))
677.80/297.12	  , addchild(node(y, ys), node(n, xs)) ->
677.80/297.12	    node(y, cons(node(n, xs), ys))
677.80/297.12	  , select(cons(ap, xs)) -> ap
677.80/297.12	  , select(cons(ap, xs)) -> select(xs) }
677.80/297.12	Obligation:
677.80/297.12	  innermost runtime complexity
677.80/297.12	Answer:
677.80/297.12	  MAYBE
677.80/297.12	
677.80/297.12	None of the processors succeeded.
677.80/297.12	
677.80/297.12	Details of failed attempt(s):
677.80/297.12	-----------------------------
677.80/297.12	1) 'empty' failed due to the following reason:
677.80/297.12	   
677.80/297.12	   Empty strict component of the problem is NOT empty.
677.80/297.12	
677.80/297.12	2) 'Best' failed due to the following reason:
677.80/297.12	   
677.80/297.12	   None of the processors succeeded.
677.80/297.12	   
677.80/297.12	   Details of failed attempt(s):
677.80/297.12	   -----------------------------
677.80/297.12	   1) 'With Problem ... (timeout of 297 seconds)' failed due to the
677.80/297.12	      following reason:
677.80/297.12	      
677.80/297.12	      Computation stopped due to timeout after 297.0 seconds.
677.80/297.12	   
677.80/297.12	   2) 'Best' failed due to the following reason:
677.80/297.12	      
677.80/297.12	      None of the processors succeeded.
677.80/297.12	      
677.80/297.12	      Details of failed attempt(s):
677.80/297.12	      -----------------------------
677.80/297.12	      1) 'With Problem ... (timeout of 148 seconds) (timeout of 297
677.80/297.12	         seconds)' failed due to the following reason:
677.80/297.12	         
677.80/297.12	         Computation stopped due to timeout after 148.0 seconds.
677.80/297.12	      
677.80/297.12	      2) 'Best' failed due to the following reason:
677.80/297.12	         
677.80/297.12	         None of the processors succeeded.
677.80/297.12	         
677.80/297.12	         Details of failed attempt(s):
677.80/297.12	         -----------------------------
677.80/297.12	         1) 'bsearch-popstar (timeout of 297 seconds)' failed due to the
677.80/297.12	            following reason:
677.80/297.12	            
677.80/297.12	            The input cannot be shown compatible
677.80/297.12	         
677.80/297.12	         2) 'Polynomial Path Order (PS) (timeout of 297 seconds)' failed due
677.80/297.12	            to the following reason:
677.80/297.12	            
677.80/297.12	            The input cannot be shown compatible
677.80/297.12	         
677.80/297.12	      
677.80/297.12	      3) 'Fastest (timeout of 24 seconds) (timeout of 297 seconds)'
677.80/297.12	         failed due to the following reason:
677.80/297.12	         
677.80/297.12	         None of the processors succeeded.
677.80/297.12	         
677.80/297.12	         Details of failed attempt(s):
677.80/297.12	         -----------------------------
677.80/297.12	         1) 'Bounds with minimal-enrichment and initial automaton 'match''
677.80/297.12	            failed due to the following reason:
677.80/297.12	            
677.80/297.12	            match-boundness of the problem could not be verified.
677.80/297.12	         
677.80/297.12	         2) 'Bounds with perSymbol-enrichment and initial automaton 'match''
677.80/297.12	            failed due to the following reason:
677.80/297.12	            
677.80/297.12	            match-boundness of the problem could not be verified.
677.80/297.12	         
677.80/297.12	      
677.80/297.12	   
677.80/297.12	
677.80/297.12	
677.80/297.12	Arrrr..
677.80/297.18	EOF