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