Surprise (networks)

From formulasearchengine
Revision as of 23:06, 18 December 2013 by 78.50.184.241 (talk)
Jump to navigation Jump to search

In proof theory, an area of mathematical logic, resolution proof reduction via local context rewriting is a technique for resolution proof reduction via local context rewriting was proposed by Simone Rollini, Roberto Bruttomesso and Natasha Sharygina in their paper "An Efficient and Flexible Approach to Resolution Proof Reduction".[1] This proof compression method was presented as an algorithm named ReduceAndReconstruct, that operates as a post-process on resolution proofs.

ReduceAndReconstruct is based on a set of local proof rewriting rules that transform a subproof into an equivalent or stronger one.[1] Each rule is defined to match a specific context.

A context (as defined by Simone et al. [1]) involves two pivots (p and q) and five clauses (α, β, γ, δ and η). The structure of a context is shown in (Template:EquationNote). Note that this imply that p is contained in β and γ (with opposite polarity) and q is contained in δ and α (also with opposite polarity).

Template:NumBlk

The table below shows the rewriting rules proposed by Simone et al..[1] The idea of the algorithm is to reduce proof size by opportunistically applying these rules.

Context Rule
Case A1: sα,tγ

stCstDtCDvar(s)tECDEvar(t)stCtEsCEvar(t)tEstDsDEvar(t)CDEvar(s)

Case A2: sα,tγ

stCsDtCDvar(s)tECDEvar(t)stCtEsCEvar(t)sDCDEvar(s)

Case B1: sα,tγ

stCstDtCDvar(s)stEsCDEvar(t)stCstEsCEvar(t)

Case B2: sα,tγ

stCsDtDCvar(s)stEsCDEvar(t)stCstEsCEvar(t)sDCDEvar(s)

Case B3: sα,tγ

stCsDtDCvar(s)stEsCDEvar(t)sD

Case A1'

stCstDtCDvar(s)tECDEvar(t)stCtEsCEvar(t)tEstDsDEvar(t)CDEvar(s)

Case B2': tγ

stCsDtCDvar(s)stEsCDEvar(t)stCstEsCEvar(t)

Note that the first five rules were introduced in an earlier paper.[2] In addition, the following is worth mentioning:

  • Rule A2 does not perform any reduction on its own. However, it is still useful, because of its "shuffling" effect that can create new opportunities for applying the other rules;
  • Rule A1 is not used in practice, because it may increase proof size;
  • Rules B1, B2, B2' and B3 are directly responsible for the reduction, as they produce a transformed root clause stronger than the original one;
  • The application of a B rule may lead to an illegal proof (see the example below), as some literals missing in the transformed root clause may be involved in another resolution step along the path to the proof root. Therefore, the algorithm also has to "reconstruct" a legal proof when this happen.

The following example (extracted from [1]) shows a situation where the proof becomes illegal after the application of B2' rule:

Template:NumBlk

Applying rule B2' to the highlighted context:

Template:NumBlk

Note that the proof is now illegal because the literal o is missing from the transformed root clause. To reconstruct the proof, one can remove o together with the last resolution step (that is now redudant). The final result is the following legal (and stronger) proof:

Template:NumBlk

Simone et al. [1] shows a further reduction of this proof by applying rule A2 to create a new opportunity to apply rule B2'.

Note that there is usually huge number of contexts where rule A2 may be applied, so an exhaustive approach is not feasible in general. Therefore, Simone et al. [1] propose to execute ReduceAndReconstruct as a loop with two termination criteria: number of iterations and a timeout (what is reached first). The pseudocode (adapted from [1]) below shows this.

 1  function ReduceAndReconstruct(π /* a proof */, timelimit, maxIterations):
 2      for i = 1 to maxIterations do
 3          ReduceAndReconstructLoop();
 4          if time > timelimit then        // timeout
 5              break;
 6      end for
 7  end function

ReduceAndReconstruct uses the function ReduceAndReconstructLoop, which is specified below. Note that the first part of the algorithm does a topological ordering of the resolution graph (considering that edges goes from antecedentes to resolvents). This is done to ensure that each node is visited after its antecedents (this way, broken resolution steps are always found and fixed).[1]

 1  function ReduceAndReconstructLoop(π /* a proof */):
 2      TS = TopologicalSorting(π);
 3      for each node n in TS
 4          if n is not a leaf
 5              if npivnclauseleft and npivnclauseright then
 6                  nclause = Resolution(nclauseleft, nclauseright);
 7                  Determine left context of n, if any;
 8                  Determine right context of n, if any;
 9                  Heuristically choose one context (if any) and apply the corresponding rule;
10              else if npivnclauseleft and npivnclauseright then
11                  Substitute n with nleft;
12              else if npivnclauseleft and npivnclauseright then
13                  Substitute n with nright;
14              else if npivnclauseleft and npivnclauseright then
15                  Heuristically choose an antecedent nleft or nright;
16                  Substitute n with nleft or nright;
17      end for
18  end function

Another point that worth mentioning is that if the input proof is not a tree (in general, resolution graphs are directed acyclic graphs), then the clause δ of a context may be involved in more than one resolution step. In this case, to ensure that an application of a rewriting rule is not going to interfere with other resolution steps, a safe solution is to create a copy of the node represented by clause δ.[1] Note that this solution increases proof size and some caution is needed when doing this.

Moreover, the heuristic for rule selection is important to achieve a good compression performance. Simone et al. [1] use the following order of preference for the rules (if applicable to the given context): B2 > B3 > { B2', B1 } > A1' > A2 (X > Y means that X is preferred over Y).

Experiments have shown that ReduceAndReconstruct alone has a worse compression/time ratio than the algorithm RecyclePivots.[3] However, while RecyclePivots can be applied only once to a proof, ReduceAndReconstruct may be applied multiple times to produce a better compression. An attempt to combine ReduceAndReconstruct and RecyclePivots algorithms has led to good results.[1]

Notes

43 year old Petroleum Engineer Harry from Deep River, usually spends time with hobbies and interests like renting movies, property developers in singapore new condominium and vehicle racing. Constantly enjoys going to destinations like Camino Real de Tierra Adentro.

  1. 1.00 1.01 1.02 1.03 1.04 1.05 1.06 1.07 1.08 1.09 1.10 1.11 Simone, S.F. ; Brutomesso, R. ; Sharygina, N. "An Efficient and Flexible Approach to Resolution Proof Reduction". 6th Haifa Verification Conference, 2010.
  2. Bruttomesso, R. ; Rollini, S. ; Sharygina, N.; Tsitovich, A. "Flexible Interpolation with Local Proof Transformations". The International Conference on Computer-Aided Design, 2010.
  3. Bar-Ilan, O. ; Fuhrmann, O. ; Hoory, S. ; Shacham, O. ; Strichman, O. "Linear-Time Reductions of Resolution Proofs". HVC, 2008.