MAYBE 933.64/297.02 MAYBE 933.64/297.02 933.64/297.02 We are left with following problem, upon which TcT provides the 933.64/297.02 certificate MAYBE. 933.64/297.02 933.64/297.02 Strict Trs: 933.64/297.02 { ack(0(), y) -> s(y) 933.64/297.02 , ack(s(x), 0()) -> ack(x, s(0())) 933.64/297.02 , ack(s(x), s(y)) -> ack(x, ack(s(x), y)) } 933.64/297.02 Obligation: 933.64/297.02 innermost runtime complexity 933.64/297.02 Answer: 933.64/297.02 MAYBE 933.64/297.02 933.64/297.02 None of the processors succeeded. 933.64/297.02 933.64/297.02 Details of failed attempt(s): 933.64/297.02 ----------------------------- 933.64/297.02 1) 'empty' failed due to the following reason: 933.64/297.02 933.64/297.02 Empty strict component of the problem is NOT empty. 933.64/297.02 933.64/297.02 2) 'Best' failed due to the following reason: 933.64/297.02 933.64/297.02 None of the processors succeeded. 933.64/297.02 933.64/297.02 Details of failed attempt(s): 933.64/297.02 ----------------------------- 933.64/297.02 1) 'With Problem ... (timeout of 297 seconds)' failed due to the 933.64/297.02 following reason: 933.64/297.02 933.64/297.02 Computation stopped due to timeout after 297.0 seconds. 933.64/297.02 933.64/297.02 2) 'Best' failed due to the following reason: 933.64/297.02 933.64/297.02 None of the processors succeeded. 933.64/297.02 933.64/297.02 Details of failed attempt(s): 933.64/297.02 ----------------------------- 933.64/297.02 1) 'With Problem ... (timeout of 148 seconds) (timeout of 297 933.64/297.02 seconds)' failed due to the following reason: 933.64/297.02 933.64/297.02 The weightgap principle applies (using the following nonconstant 933.64/297.02 growth matrix-interpretation) 933.64/297.02 933.64/297.02 The following argument positions are usable: 933.64/297.02 Uargs(ack) = {2} 933.64/297.02 933.64/297.02 TcT has computed the following matrix interpretation satisfying 933.64/297.02 not(EDA) and not(IDA(1)). 933.64/297.02 933.64/297.02 [ack](x1, x2) = [1] x2 + [0] 933.64/297.02 933.64/297.02 [0] = [0] 933.64/297.02 933.64/297.02 [s](x1) = [1] x1 + [1] 933.64/297.02 933.64/297.02 The order satisfies the following ordering constraints: 933.64/297.02 933.64/297.02 [ack(0(), y)] = [1] y + [0] 933.64/297.02 ? [1] y + [1] 933.64/297.02 = [s(y)] 933.64/297.02 933.64/297.02 [ack(s(x), 0())] = [0] 933.64/297.02 ? [1] 933.64/297.02 = [ack(x, s(0()))] 933.64/297.02 933.64/297.02 [ack(s(x), s(y))] = [1] y + [1] 933.64/297.02 > [1] y + [0] 933.64/297.02 = [ack(x, ack(s(x), y))] 933.64/297.02 933.64/297.02 933.64/297.02 Further, it can be verified that all rules not oriented are covered by the weightgap condition. 933.64/297.02 933.64/297.02 We are left with following problem, upon which TcT provides the 933.64/297.02 certificate MAYBE. 933.64/297.02 933.64/297.02 Strict Trs: 933.64/297.02 { ack(0(), y) -> s(y) 933.64/297.02 , ack(s(x), 0()) -> ack(x, s(0())) } 933.64/297.02 Weak Trs: { ack(s(x), s(y)) -> ack(x, ack(s(x), y)) } 933.64/297.02 Obligation: 933.64/297.02 innermost runtime complexity 933.64/297.02 Answer: 933.64/297.02 MAYBE 933.64/297.02 933.64/297.02 None of the processors succeeded. 933.64/297.02 933.64/297.02 Details of failed attempt(s): 933.64/297.02 ----------------------------- 933.64/297.02 1) 'empty' failed due to the following reason: 933.64/297.02 933.64/297.02 Empty strict component of the problem is NOT empty. 933.64/297.02 933.64/297.02 2) 'With Problem ...' failed due to the following reason: 933.64/297.02 933.64/297.02 None of the processors succeeded. 933.64/297.02 933.64/297.02 Details of failed attempt(s): 933.64/297.02 ----------------------------- 933.64/297.02 1) 'empty' failed due to the following reason: 933.64/297.02 933.64/297.02 Empty strict component of the problem is NOT empty. 933.64/297.02 933.64/297.02 2) 'Fastest' failed due to the following reason: 933.64/297.02 933.64/297.02 None of the processors succeeded. 933.64/297.02 933.64/297.02 Details of failed attempt(s): 933.64/297.02 ----------------------------- 933.64/297.02 1) 'With Problem ...' failed due to the following reason: 933.64/297.02 933.64/297.02 None of the processors succeeded. 933.64/297.02 933.64/297.02 Details of failed attempt(s): 933.64/297.02 ----------------------------- 933.64/297.02 1) 'empty' failed due to the following reason: 933.64/297.02 933.64/297.02 Empty strict component of the problem is NOT empty. 933.64/297.02 933.64/297.02 2) 'With Problem ...' failed due to the following reason: 933.64/297.02 933.64/297.02 Empty strict component of the problem is NOT empty. 933.64/297.02 933.64/297.02 933.64/297.02 2) 'With Problem ...' failed due to the following reason: 933.64/297.02 933.64/297.02 None of the processors succeeded. 933.64/297.02 933.64/297.02 Details of failed attempt(s): 933.64/297.02 ----------------------------- 933.64/297.02 1) 'empty' failed due to the following reason: 933.64/297.02 933.64/297.02 Empty strict component of the problem is NOT empty. 933.64/297.02 933.64/297.02 2) 'With Problem ...' failed due to the following reason: 933.64/297.02 933.64/297.02 None of the processors succeeded. 933.64/297.02 933.64/297.02 Details of failed attempt(s): 933.64/297.02 ----------------------------- 933.64/297.02 1) 'empty' failed due to the following reason: 933.64/297.02 933.64/297.02 Empty strict component of the problem is NOT empty. 933.64/297.02 933.64/297.02 2) 'With Problem ...' failed due to the following reason: 933.64/297.02 933.64/297.02 None of the processors succeeded. 933.64/297.02 933.64/297.02 Details of failed attempt(s): 933.64/297.02 ----------------------------- 933.64/297.02 1) 'empty' failed due to the following reason: 933.64/297.02 933.64/297.02 Empty strict component of the problem is NOT empty. 933.64/297.02 933.64/297.02 2) 'With Problem ...' failed due to the following reason: 933.64/297.02 933.64/297.02 Empty strict component of the problem is NOT empty. 933.64/297.02 933.64/297.02 933.64/297.02 933.64/297.02 933.64/297.02 933.64/297.02 933.64/297.02 933.64/297.02 2) 'Best' failed due to the following reason: 933.64/297.02 933.64/297.02 None of the processors succeeded. 933.64/297.02 933.64/297.02 Details of failed attempt(s): 933.64/297.02 ----------------------------- 933.64/297.02 1) 'bsearch-popstar (timeout of 297 seconds)' failed due to the 933.64/297.02 following reason: 933.64/297.02 933.64/297.02 The input cannot be shown compatible 933.64/297.02 933.64/297.02 2) 'Polynomial Path Order (PS) (timeout of 297 seconds)' failed due 933.64/297.02 to the following reason: 933.64/297.02 933.64/297.02 The input cannot be shown compatible 933.64/297.02 933.64/297.02 933.64/297.02 3) 'Fastest (timeout of 24 seconds) (timeout of 297 seconds)' 933.64/297.02 failed due to the following reason: 933.64/297.02 933.64/297.02 None of the processors succeeded. 933.64/297.02 933.64/297.02 Details of failed attempt(s): 933.64/297.02 ----------------------------- 933.64/297.02 1) 'Bounds with minimal-enrichment and initial automaton 'match'' 933.64/297.02 failed due to the following reason: 933.64/297.02 933.64/297.02 match-boundness of the problem could not be verified. 933.64/297.02 933.64/297.02 2) 'Bounds with perSymbol-enrichment and initial automaton 'match'' 933.64/297.02 failed due to the following reason: 933.64/297.02 933.64/297.02 match-boundness of the problem could not be verified. 933.64/297.02 933.64/297.02 933.64/297.02 933.64/297.02 933.64/297.02 933.64/297.02 Arrrr.. 934.18/297.60 EOF