MAYBE
910.14/297.02	MAYBE
910.14/297.02	
910.14/297.02	We are left with following problem, upon which TcT provides the
910.14/297.02	certificate MAYBE.
910.14/297.02	
910.14/297.02	Strict Trs:
910.14/297.02	  { not(not(x)) -> x
910.14/297.02	  , not(or(x, y)) -> and(not(not(not(x))), not(not(not(y))))
910.14/297.02	  , not(and(x, y)) -> or(not(not(not(x))), not(not(not(y)))) }
910.14/297.02	Obligation:
910.14/297.02	  runtime complexity
910.14/297.02	Answer:
910.14/297.02	  MAYBE
910.14/297.02	
910.14/297.02	None of the processors succeeded.
910.14/297.02	
910.14/297.02	Details of failed attempt(s):
910.14/297.02	-----------------------------
910.14/297.02	1) 'With Problem ... (timeout of 297 seconds)' failed due to the
910.14/297.02	   following reason:
910.14/297.02	   
910.14/297.02	   Computation stopped due to timeout after 297.0 seconds.
910.14/297.02	
910.14/297.02	2) 'Best' failed due to the following reason:
910.14/297.02	   
910.14/297.02	   None of the processors succeeded.
910.14/297.02	   
910.14/297.02	   Details of failed attempt(s):
910.14/297.02	   -----------------------------
910.14/297.02	   1) 'With Problem ... (timeout of 148 seconds) (timeout of 297
910.14/297.02	      seconds)' failed due to the following reason:
910.14/297.02	      
910.14/297.02	      Computation stopped due to timeout after 148.0 seconds.
910.14/297.02	   
910.14/297.02	   2) 'Fastest (timeout of 24 seconds) (timeout of 297 seconds)'
910.14/297.02	      failed due to the following reason:
910.14/297.02	      
910.14/297.02	      Computation stopped due to timeout after 24.0 seconds.
910.14/297.02	   
910.14/297.02	   3) 'Best' failed due to the following reason:
910.14/297.02	      
910.14/297.02	      None of the processors succeeded.
910.14/297.02	      
910.14/297.02	      Details of failed attempt(s):
910.14/297.02	      -----------------------------
910.14/297.02	      1) 'bsearch-popstar (timeout of 297 seconds)' failed due to the
910.14/297.02	         following reason:
910.14/297.02	         
910.14/297.02	         The processor is inapplicable, reason:
910.14/297.02	           Processor only applicable for innermost runtime complexity analysis
910.14/297.02	      
910.14/297.02	      2) 'Polynomial Path Order (PS) (timeout of 297 seconds)' failed due
910.14/297.02	         to the following reason:
910.14/297.02	         
910.14/297.02	         The processor is inapplicable, reason:
910.14/297.02	           Processor only applicable for innermost runtime complexity analysis
910.14/297.02	      
910.14/297.02	   
910.14/297.02	
910.14/297.02	3) 'Weak Dependency Pairs (timeout of 297 seconds)' failed due to
910.14/297.02	   the following reason:
910.14/297.02	   
910.14/297.02	   We add the following weak dependency pairs:
910.14/297.02	   
910.14/297.02	   Strict DPs:
910.14/297.02	     { not^#(not(x)) -> c_1(x)
910.14/297.02	     , not^#(or(x, y)) -> c_2(not^#(not(not(x))), not^#(not(not(y))))
910.14/297.02	     , not^#(and(x, y)) -> c_3(not^#(not(not(x))), not^#(not(not(y)))) }
910.14/297.02	   
910.14/297.02	   and mark the set of starting terms.
910.14/297.02	   
910.14/297.02	   We are left with following problem, upon which TcT provides the
910.14/297.02	   certificate MAYBE.
910.14/297.02	   
910.14/297.02	   Strict DPs:
910.14/297.02	     { not^#(not(x)) -> c_1(x)
910.14/297.02	     , not^#(or(x, y)) -> c_2(not^#(not(not(x))), not^#(not(not(y))))
910.14/297.02	     , not^#(and(x, y)) -> c_3(not^#(not(not(x))), not^#(not(not(y)))) }
910.14/297.02	   Strict Trs:
910.14/297.02	     { not(not(x)) -> x
910.14/297.02	     , not(or(x, y)) -> and(not(not(not(x))), not(not(not(y))))
910.14/297.02	     , not(and(x, y)) -> or(not(not(not(x))), not(not(not(y)))) }
910.14/297.02	   Obligation:
910.14/297.02	     runtime complexity
910.14/297.02	   Answer:
910.14/297.02	     MAYBE
910.14/297.02	   
910.14/297.02	   Empty strict component of the problem is NOT empty.
910.14/297.02	
910.14/297.02	
910.14/297.02	Arrrr..
910.24/297.18	EOF