/export/starexec/sandbox/solver/bin/starexec_run_HigherOrder /export/starexec/sandbox/benchmark/theBenchmark.xml /export/starexec/sandbox/output/output_files -------------------------------------------------------------------------------- YES We consider the system theBenchmark. Alphabet: 0 : [] --> a cons : [c * c] --> c copy : [a * c * c] --> c f : [c] --> c false : [] --> b filter : [c -> b * c] --> c filter2 : [b * c -> b * c * c] --> c map : [c -> c * c] --> c n : [] --> a nil : [] --> c s : [a] --> a true : [] --> b Rules: f(cons(nil, x)) => x f(cons(f(cons(nil, x)), y)) => copy(n, x, y) copy(0, x, y) => f(y) copy(s(x), y, z) => copy(x, y, cons(f(y), z)) map(g, nil) => nil map(g, cons(x, y)) => cons(g x, map(g, y)) filter(g, nil) => nil filter(g, cons(x, y)) => filter2(g x, g, x, y) filter2(true, g, x, y) => cons(x, filter(g, y)) filter2(false, g, x, y) => filter(g, y) This AFS is converted to an AFSM simply by replacing all free variables by meta-variables (with arity 0). We observe that the rules contain a first-order subset: f(cons(nil, X)) => X f(cons(f(cons(nil, X)), Y)) => copy(n, X, Y) copy(0, X, Y) => f(Y) copy(s(X), Y, Z) => copy(X, Y, cons(f(Y), Z)) Moreover, the system is finitely branching. Thus, by [Kop12, Thm. 7.55], we may omit all first-order dependency pairs from the dependency pair problem (DP(R), R) if this first-order part is Ce-terminating when seen as a many-sorted first-order TRS. According to the external first-order termination prover, this system is indeed Ce-terminating: || proof of resources/system.trs || # AProVE Commit ID: d84c10301d352dfd14de2104819581f4682260f5 fuhs 20130616 || || || Termination w.r.t. Q of the given QTRS could be proven: || || (0) QTRS || (1) DependencyPairsProof [EQUIVALENT] || (2) QDP || (3) DependencyGraphProof [EQUIVALENT] || (4) QDP || (5) QDPSizeChangeProof [EQUIVALENT] || (6) YES || || || ---------------------------------------- || || (0) || Obligation: || Q restricted rewrite system: || The TRS R consists of the following rules: || || f(cons(nil, %X)) -> %X || f(cons(f(cons(nil, %X)), %Y)) -> copy(n, %X, %Y) || copy(0, %X, %Y) -> f(%Y) || copy(s(%X), %Y, %Z) -> copy(%X, %Y, cons(f(%Y), %Z)) || ~PAIR(%X, %Y) -> %X || ~PAIR(%X, %Y) -> %Y || || Q is empty. || || ---------------------------------------- || || (1) DependencyPairsProof (EQUIVALENT) || Using Dependency Pairs [AG00,LPAR04] we result in the following initial DP problem. || ---------------------------------------- || || (2) || Obligation: || Q DP problem: || The TRS P consists of the following rules: || || F(cons(f(cons(nil, %X)), %Y)) -> COPY(n, %X, %Y) || COPY(0, %X, %Y) -> F(%Y) || COPY(s(%X), %Y, %Z) -> COPY(%X, %Y, cons(f(%Y), %Z)) || COPY(s(%X), %Y, %Z) -> F(%Y) || || The TRS R consists of the following rules: || || f(cons(nil, %X)) -> %X || f(cons(f(cons(nil, %X)), %Y)) -> copy(n, %X, %Y) || copy(0, %X, %Y) -> f(%Y) || copy(s(%X), %Y, %Z) -> copy(%X, %Y, cons(f(%Y), %Z)) || ~PAIR(%X, %Y) -> %X || ~PAIR(%X, %Y) -> %Y || || Q is empty. || We have to consider all minimal (P,Q,R)-chains. || ---------------------------------------- || || (3) DependencyGraphProof (EQUIVALENT) || The approximation of the Dependency Graph [LPAR04,FROCOS05,EDGSTAR] contains 1 SCC with 3 less nodes. || ---------------------------------------- || || (4) || Obligation: || Q DP problem: || The TRS P consists of the following rules: || || COPY(s(%X), %Y, %Z) -> COPY(%X, %Y, cons(f(%Y), %Z)) || || The TRS R consists of the following rules: || || f(cons(nil, %X)) -> %X || f(cons(f(cons(nil, %X)), %Y)) -> copy(n, %X, %Y) || copy(0, %X, %Y) -> f(%Y) || copy(s(%X), %Y, %Z) -> copy(%X, %Y, cons(f(%Y), %Z)) || ~PAIR(%X, %Y) -> %X || ~PAIR(%X, %Y) -> %Y || || Q is empty. || We have to consider all minimal (P,Q,R)-chains. || ---------------------------------------- || || (5) QDPSizeChangeProof (EQUIVALENT) || By using the subterm criterion [SUBTERM_CRITERION] together with the size-change analysis [AAECC05] we have proven that there are no infinite chains for this DP problem. || || From the DPs we obtained the following set of size-change graphs: || *COPY(s(%X), %Y, %Z) -> COPY(%X, %Y, cons(f(%Y), %Z)) || The graph contains the following edges 1 > 1, 2 >= 2 || || || ---------------------------------------- || || (6) || YES || We use the dependency pair framework as described in [Kop12, Ch. 6/7], with static dependency pairs (see [KusIsoSakBla09] and the adaptation for AFSMs in [Kop12, Ch. 7.8]). We thus obtain the following dependency pair problem (P_0, R_0, minimal, formative): Dependency Pairs P_0: 0] map#(F, cons(X, Y)) =#> map#(F, Y) 1] filter#(F, cons(X, Y)) =#> filter2#(F X, F, X, Y) 2] filter2#(true, F, X, Y) =#> filter#(F, Y) 3] filter2#(false, F, X, Y) =#> filter#(F, Y) Rules R_0: f(cons(nil, X)) => X f(cons(f(cons(nil, X)), Y)) => copy(n, X, Y) copy(0, X, Y) => f(Y) copy(s(X), Y, Z) => copy(X, Y, cons(f(Y), Z)) map(F, nil) => nil map(F, cons(X, Y)) => cons(F X, map(F, Y)) filter(F, nil) => nil filter(F, cons(X, Y)) => filter2(F X, F, X, Y) filter2(true, F, X, Y) => cons(X, filter(F, Y)) filter2(false, F, X, Y) => filter(F, Y) Thus, the original system is terminating if (P_0, R_0, minimal, formative) is finite. We consider the dependency pair problem (P_0, R_0, minimal, formative). We place the elements of P in a dependency graph approximation G (see e.g. [Kop12, Thm. 7.27, 7.29], as follows: * 0 : 0 * 1 : 2, 3 * 2 : 1 * 3 : 1 This graph has the following strongly connected components: P_1: map#(F, cons(X, Y)) =#> map#(F, Y) P_2: filter#(F, cons(X, Y)) =#> filter2#(F X, F, X, Y) filter2#(true, F, X, Y) =#> filter#(F, Y) filter2#(false, F, X, Y) =#> filter#(F, Y) By [Kop12, Thm. 7.31], we may replace any dependency pair problem (P_0, R_0, m, f) by (P_1, R_0, m, f) and (P_2, R_0, m, f). Thus, the original system is terminating if each of (P_1, R_0, minimal, formative) and (P_2, R_0, minimal, formative) is finite. We consider the dependency pair problem (P_2, R_0, minimal, formative). We apply the subterm criterion with the following projection function: nu(filter2#) = 4 nu(filter#) = 2 Thus, we can orient the dependency pairs as follows: nu(filter#(F, cons(X, Y))) = cons(X, Y) |> Y = nu(filter2#(F X, F, X, Y)) nu(filter2#(true, F, X, Y)) = Y = Y = nu(filter#(F, Y)) nu(filter2#(false, F, X, Y)) = Y = Y = nu(filter#(F, Y)) By [Kop12, Thm. 7.35], we may replace a dependency pair problem (P_2, R_0, minimal, f) by (P_3, R_0, minimal, f), where P_3 contains: filter2#(true, F, X, Y) =#> filter#(F, Y) filter2#(false, F, X, Y) =#> filter#(F, Y) Thus, the original system is terminating if each of (P_1, R_0, minimal, formative) and (P_3, R_0, minimal, formative) is finite. We consider the dependency pair problem (P_3, R_0, minimal, formative). We place the elements of P in a dependency graph approximation G (see e.g. [Kop12, Thm. 7.27, 7.29], as follows: * 0 : * 1 : This graph has no strongly connected components. By [Kop12, Thm. 7.31], this implies finiteness of the dependency pair problem. Thus, the original system is terminating if (P_1, R_0, minimal, formative) is finite. We consider the dependency pair problem (P_1, R_0, minimal, formative). We apply the subterm criterion with the following projection function: nu(map#) = 2 Thus, we can orient the dependency pairs as follows: nu(map#(F, cons(X, Y))) = cons(X, Y) |> Y = nu(map#(F, Y)) By [Kop12, Thm. 7.35], we may replace a dependency pair problem (P_1, R_0, minimal, f) by ({}, R_0, minimal, f). By the empty set processor [Kop12, Thm. 7.15] this problem may be immediately removed. As all dependency pair problems were succesfully simplified with sound (and complete) processors until nothing remained, we conclude termination. +++ Citations +++ [Kop12] C. Kop. Higher Order Termination. PhD Thesis, 2012. [KusIsoSakBla09] K. Kusakari, Y. Isogai, M. Sakai, and F. Blanqui. Static Dependency Pair Method Based On Strong Computability for Higher-Order Rewrite Systems. In volume 92(10) of IEICE Transactions on Information and Systems. 2007--2015, 2009.