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