MAYBE
1184.75/297.13	MAYBE
1184.75/297.13	
1184.75/297.13	We are left with following problem, upon which TcT provides the
1184.75/297.13	certificate MAYBE.
1184.75/297.13	
1184.75/297.13	Strict Trs:
1184.75/297.13	  { a__f(X) -> f(X)
1184.75/297.13	  , a__f(0()) -> cons(0(), f(s(0())))
1184.75/297.13	  , a__f(s(0())) -> a__f(a__p(s(0())))
1184.75/297.13	  , a__p(X) -> p(X)
1184.75/297.13	  , a__p(s(X)) -> mark(X)
1184.75/297.13	  , mark(0()) -> 0()
1184.75/297.13	  , mark(cons(X1, X2)) -> cons(mark(X1), X2)
1184.75/297.13	  , mark(f(X)) -> a__f(mark(X))
1184.75/297.13	  , mark(s(X)) -> s(mark(X))
1184.75/297.13	  , mark(p(X)) -> a__p(mark(X)) }
1184.75/297.13	Obligation:
1184.75/297.13	  derivational complexity
1184.75/297.13	Answer:
1184.75/297.13	  MAYBE
1184.75/297.13	
1184.75/297.13	None of the processors succeeded.
1184.75/297.13	
1184.75/297.13	Details of failed attempt(s):
1184.75/297.13	-----------------------------
1184.75/297.13	1) 'iteProgress (timeout of 297 seconds)' failed due to the
1184.75/297.13	   following reason:
1184.75/297.13	   
1184.75/297.13	   Computation stopped due to timeout after 297.0 seconds.
1184.75/297.13	
1184.75/297.13	2) 'Inspecting Problem... (timeout of 297 seconds)' failed due to
1184.75/297.13	   the following reason:
1184.75/297.13	   
1184.75/297.13	   Computation stopped due to timeout after 297.0 seconds.
1184.75/297.13	
1184.75/297.13	3) 'Fastest (timeout of 60 seconds)' failed due to the following
1184.75/297.13	   reason:
1184.75/297.13	   
1184.75/297.13	   Computation stopped due to timeout after 60.0 seconds.
1184.75/297.13	
1184.75/297.13	4) 'bsearch-matrix (timeout of 297 seconds)' failed due to the
1184.75/297.13	   following reason:
1184.75/297.13	   
1184.75/297.13	   The input cannot be shown compatible
1184.75/297.13	
1184.75/297.13	
1184.75/297.13	Arrrr..
1184.75/297.17	EOF