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