MAYBE 884.94/297.10 MAYBE 884.94/297.10 884.94/297.10 We are left with following problem, upon which TcT provides the 884.94/297.10 certificate MAYBE. 884.94/297.10 884.94/297.10 Strict Trs: 884.94/297.10 { active(f(x, y, z)) -> f(x, y, active(z)) 884.94/297.10 , active(f(b(), c(), x)) -> mark(f(x, x, x)) 884.94/297.10 , active(d()) -> mark(c()) 884.94/297.10 , active(d()) -> m(b()) 884.94/297.10 , f(x, y, mark(z)) -> mark(f(x, y, z)) 884.94/297.10 , f(ok(x), ok(y), ok(z)) -> ok(f(x, y, z)) 884.94/297.10 , proper(f(x, y, z)) -> f(proper(x), proper(y), proper(z)) 884.94/297.10 , proper(b()) -> ok(b()) 884.94/297.10 , proper(c()) -> ok(c()) 884.94/297.10 , proper(d()) -> ok(d()) 884.94/297.10 , top(mark(x)) -> top(proper(x)) 884.94/297.10 , top(ok(x)) -> top(active(x)) } 884.94/297.10 Obligation: 884.94/297.10 innermost runtime complexity 884.94/297.10 Answer: 884.94/297.10 MAYBE 884.94/297.10 884.94/297.10 None of the processors succeeded. 884.94/297.10 884.94/297.10 Details of failed attempt(s): 884.94/297.10 ----------------------------- 884.94/297.10 1) 'empty' failed due to the following reason: 884.94/297.10 884.94/297.10 Empty strict component of the problem is NOT empty. 884.94/297.10 884.94/297.10 2) 'Best' failed due to the following reason: 884.94/297.10 884.94/297.10 None of the processors succeeded. 884.94/297.10 884.94/297.10 Details of failed attempt(s): 884.94/297.10 ----------------------------- 884.94/297.10 1) 'With Problem ... (timeout of 297 seconds)' failed due to the 884.94/297.10 following reason: 884.94/297.10 884.94/297.10 Computation stopped due to timeout after 297.0 seconds. 884.94/297.10 884.94/297.10 2) 'Best' failed due to the following reason: 884.94/297.10 884.94/297.10 None of the processors succeeded. 884.94/297.10 884.94/297.10 Details of failed attempt(s): 884.94/297.10 ----------------------------- 884.94/297.10 1) 'With Problem ... (timeout of 148 seconds) (timeout of 297 884.94/297.10 seconds)' failed due to the following reason: 884.94/297.10 884.94/297.10 Computation stopped due to timeout after 148.0 seconds. 884.94/297.10 884.94/297.10 2) 'Best' failed due to the following reason: 884.94/297.10 884.94/297.10 None of the processors succeeded. 884.94/297.10 884.94/297.10 Details of failed attempt(s): 884.94/297.10 ----------------------------- 884.94/297.10 1) 'bsearch-popstar (timeout of 297 seconds)' failed due to the 884.94/297.10 following reason: 884.94/297.10 884.94/297.10 The input cannot be shown compatible 884.94/297.10 884.94/297.10 2) 'Polynomial Path Order (PS) (timeout of 297 seconds)' failed due 884.94/297.10 to the following reason: 884.94/297.10 884.94/297.10 The input cannot be shown compatible 884.94/297.10 884.94/297.10 884.94/297.10 3) 'Fastest (timeout of 24 seconds) (timeout of 297 seconds)' 884.94/297.10 failed due to the following reason: 884.94/297.10 884.94/297.10 None of the processors succeeded. 884.94/297.10 884.94/297.10 Details of failed attempt(s): 884.94/297.10 ----------------------------- 884.94/297.10 1) 'Bounds with minimal-enrichment and initial automaton 'match'' 884.94/297.10 failed due to the following reason: 884.94/297.10 884.94/297.10 match-boundness of the problem could not be verified. 884.94/297.10 884.94/297.10 2) 'Bounds with perSymbol-enrichment and initial automaton 'match'' 884.94/297.10 failed due to the following reason: 884.94/297.10 884.94/297.10 match-boundness of the problem could not be verified. 884.94/297.10 884.94/297.10 884.94/297.10 884.94/297.10 884.94/297.10 884.94/297.10 Arrrr.. 884.94/297.13 EOF