MAYBE 817.51/297.03 MAYBE 817.51/297.03 817.51/297.03 We are left with following problem, upon which TcT provides the 817.51/297.03 certificate MAYBE. 817.51/297.03 817.51/297.03 Strict Trs: 817.51/297.03 { a__f(X1, X2) -> f(X1, X2) 817.51/297.03 , a__f(g(X), Y) -> a__f(mark(X), f(g(X), Y)) 817.51/297.03 , mark(g(X)) -> g(mark(X)) 817.51/297.03 , mark(f(X1, X2)) -> a__f(mark(X1), X2) } 817.51/297.03 Obligation: 817.51/297.03 runtime complexity 817.51/297.03 Answer: 817.51/297.03 MAYBE 817.51/297.03 817.51/297.03 None of the processors succeeded. 817.51/297.03 817.51/297.03 Details of failed attempt(s): 817.51/297.03 ----------------------------- 817.51/297.03 1) 'With Problem ... (timeout of 297 seconds)' failed due to the 817.51/297.03 following reason: 817.51/297.03 817.51/297.03 Computation stopped due to timeout after 297.0 seconds. 817.51/297.03 817.51/297.03 2) 'Best' failed due to the following reason: 817.51/297.03 817.51/297.03 None of the processors succeeded. 817.51/297.03 817.51/297.03 Details of failed attempt(s): 817.51/297.03 ----------------------------- 817.51/297.03 1) 'With Problem ... (timeout of 148 seconds) (timeout of 297 817.51/297.03 seconds)' failed due to the following reason: 817.51/297.03 817.51/297.03 None of the processors succeeded. 817.51/297.03 817.51/297.03 Details of failed attempt(s): 817.51/297.03 ----------------------------- 817.51/297.03 1) 'empty' failed due to the following reason: 817.51/297.03 817.51/297.03 Empty strict component of the problem is NOT empty. 817.51/297.03 817.51/297.03 2) 'With Problem ...' failed due to the following reason: 817.51/297.03 817.51/297.03 None of the processors succeeded. 817.51/297.03 817.51/297.03 Details of failed attempt(s): 817.51/297.03 ----------------------------- 817.51/297.03 1) 'empty' failed due to the following reason: 817.51/297.03 817.51/297.03 Empty strict component of the problem is NOT empty. 817.51/297.03 817.51/297.03 2) 'Fastest' failed due to the following reason: 817.51/297.03 817.51/297.03 None of the processors succeeded. 817.51/297.03 817.51/297.03 Details of failed attempt(s): 817.51/297.03 ----------------------------- 817.51/297.03 1) 'With Problem ...' failed due to the following reason: 817.51/297.03 817.51/297.03 None of the processors succeeded. 817.51/297.03 817.51/297.03 Details of failed attempt(s): 817.51/297.03 ----------------------------- 817.51/297.03 1) 'empty' failed due to the following reason: 817.51/297.03 817.51/297.03 Empty strict component of the problem is NOT empty. 817.51/297.03 817.51/297.03 2) 'With Problem ...' failed due to the following reason: 817.51/297.03 817.51/297.03 None of the processors succeeded. 817.51/297.03 817.51/297.03 Details of failed attempt(s): 817.51/297.03 ----------------------------- 817.51/297.03 1) 'empty' failed due to the following reason: 817.51/297.03 817.51/297.03 Empty strict component of the problem is NOT empty. 817.51/297.03 817.51/297.03 2) 'With Problem ...' failed due to the following reason: 817.51/297.03 817.51/297.03 None of the processors succeeded. 817.51/297.03 817.51/297.03 Details of failed attempt(s): 817.51/297.03 ----------------------------- 817.51/297.03 1) 'empty' failed due to the following reason: 817.51/297.03 817.51/297.03 Empty strict component of the problem is NOT empty. 817.51/297.03 817.51/297.03 2) 'With Problem ...' failed due to the following reason: 817.51/297.03 817.51/297.03 Empty strict component of the problem is NOT empty. 817.51/297.03 817.51/297.03 817.51/297.03 817.51/297.03 817.51/297.03 2) 'With Problem ...' failed due to the following reason: 817.51/297.03 817.51/297.03 None of the processors succeeded. 817.51/297.03 817.51/297.03 Details of failed attempt(s): 817.51/297.03 ----------------------------- 817.51/297.03 1) 'empty' failed due to the following reason: 817.51/297.03 817.51/297.03 Empty strict component of the problem is NOT empty. 817.51/297.03 817.51/297.03 2) 'With Problem ...' failed due to the following reason: 817.51/297.03 817.51/297.03 Empty strict component of the problem is NOT empty. 817.51/297.03 817.51/297.03 817.51/297.03 817.51/297.03 817.51/297.03 817.51/297.03 2) 'Fastest (timeout of 24 seconds) (timeout of 297 seconds)' 817.51/297.03 failed due to the following reason: 817.51/297.03 817.51/297.03 None of the processors succeeded. 817.51/297.03 817.51/297.03 Details of failed attempt(s): 817.51/297.03 ----------------------------- 817.51/297.03 1) 'Bounds with minimal-enrichment and initial automaton 'match'' 817.51/297.03 failed due to the following reason: 817.51/297.03 817.51/297.03 match-boundness of the problem could not be verified. 817.51/297.03 817.51/297.03 2) 'Bounds with perSymbol-enrichment and initial automaton 'match'' 817.51/297.03 failed due to the following reason: 817.51/297.03 817.51/297.03 match-boundness of the problem could not be verified. 817.51/297.03 817.51/297.03 817.51/297.03 3) 'Best' failed due to the following reason: 817.51/297.03 817.51/297.03 None of the processors succeeded. 817.51/297.03 817.51/297.03 Details of failed attempt(s): 817.51/297.03 ----------------------------- 817.51/297.03 1) 'bsearch-popstar (timeout of 297 seconds)' failed due to the 817.51/297.03 following reason: 817.51/297.03 817.51/297.03 The processor is inapplicable, reason: 817.51/297.03 Processor only applicable for innermost runtime complexity analysis 817.51/297.03 817.51/297.03 2) 'Polynomial Path Order (PS) (timeout of 297 seconds)' failed due 817.51/297.03 to the following reason: 817.51/297.03 817.51/297.03 The processor is inapplicable, reason: 817.51/297.03 Processor only applicable for innermost runtime complexity analysis 817.51/297.03 817.51/297.03 817.51/297.03 817.51/297.03 3) 'Weak Dependency Pairs (timeout of 297 seconds)' failed due to 817.51/297.03 the following reason: 817.51/297.03 817.51/297.03 We add the following weak dependency pairs: 817.51/297.03 817.51/297.03 Strict DPs: 817.51/297.03 { a__f^#(X1, X2) -> c_1(X1, X2) 817.51/297.03 , a__f^#(g(X), Y) -> c_2(a__f^#(mark(X), f(g(X), Y))) 817.51/297.03 , mark^#(g(X)) -> c_3(mark^#(X)) 817.51/297.03 , mark^#(f(X1, X2)) -> c_4(a__f^#(mark(X1), X2)) } 817.51/297.03 817.51/297.03 and mark the set of starting terms. 817.51/297.03 817.51/297.03 We are left with following problem, upon which TcT provides the 817.51/297.03 certificate MAYBE. 817.51/297.03 817.51/297.03 Strict DPs: 817.51/297.03 { a__f^#(X1, X2) -> c_1(X1, X2) 817.51/297.03 , a__f^#(g(X), Y) -> c_2(a__f^#(mark(X), f(g(X), Y))) 817.51/297.03 , mark^#(g(X)) -> c_3(mark^#(X)) 817.51/297.03 , mark^#(f(X1, X2)) -> c_4(a__f^#(mark(X1), X2)) } 817.51/297.03 Strict Trs: 817.51/297.03 { a__f(X1, X2) -> f(X1, X2) 817.51/297.03 , a__f(g(X), Y) -> a__f(mark(X), f(g(X), Y)) 817.51/297.03 , mark(g(X)) -> g(mark(X)) 817.51/297.03 , mark(f(X1, X2)) -> a__f(mark(X1), X2) } 817.51/297.03 Obligation: 817.51/297.03 runtime complexity 817.51/297.03 Answer: 817.51/297.03 MAYBE 817.51/297.03 817.51/297.03 Empty strict component of the problem is NOT empty. 817.51/297.03 817.51/297.03 817.51/297.03 Arrrr.. 818.16/297.66 EOF