Difference between pages "New Proof Rules" and "New Tactic Providers"

From Event-B
(Difference between pages)
Jump to navigationJump to search
imported>Mathieu
 
imported>Nicolas
m (Page bootstrap)
 
Line 1: Line 1:
This document describes the set of newly added reasoners for improving the usability of the prover within Rodin Platform. The work has been done originally by Stephan Merkli, Michael Schaufelberger and David Simmen as their project for an object oriented programming course at ETH Zürich. The aim of the work is to try out the extensibility feature of the RODIN platform related to the prover.  The rules are added using as various plug-ins with most of the work done in a declarative fashion. Moreover the new features are also tested using the pre-defined framework which has been set-up during the development of the RODIN platform. The rules are of different types: automatic/interactive rewriting or more general inference rules.
+
The purpose is to give more flexibility to tactic providers by allowing them to provide as many tactic applications as they will for a given proof node, even they apply to the same predicate and at the same position.  
  
 +
=== Proposed Framework ===
  
==Remove Membership for Range==
+
public interface ITacticProvider2 {
 +
    List<ITacticApplication> getPossibleApplications(IUserSupport userSupport,
 +
                                                    IProofTreeNode node,
 +
                                                    Predicate hyp,
 +
                                                    String globalInput);
 +
}
  
The work is related to the following rewriting rule:
 
  
<math> E \in a \upto b ~~~\mathrel{\widehat{=}}~~~ a \leq E ~\land~ E \leq b  </math>
+
  public interface ITacticApplication {
 +
    void apply(String[] inputs, String globalInput, IProgressMonitor monitor);
 +
  }
  
The rule has been implemented so that it can be applied both automatically and interactively.
 
  
* Automatically: The rule can be chosen from the Preferences of the Sequent Prover to be run as a part of the Automatic Prover or as a part of the Post-Tactic. The rewriting is carried out to all sub-formulas of the form <math>E \in a \upto b</math>.
+
  public interface IPositionApplication  extends ITacticApplication {
 +
    Point getHyperlinkBounds();
 +
    String getHyperlinkLabel();
 +
}
  
* Interactively: The <math>\in</math> symbol is redden in the formular (either goal or hypotheses) and is applied only to the sub-formula as indicated by the user.
+
  public interface IPredicateApplication extends ITacticApplication {
 
+
    Image getIcon();
 
+
    String getTip();
==Automatic Rule for Overriding==
+
  }
 
 
The work is related to the following rewriting rule:
 
 
 
<math>  p \ovl \ldots \ovl \emptyset \ovl \ldots q  ~~~\mathrel{\widehat{=}}~~~ p \ovl \ldots \ovl q  </math>
 
 
 
(i.e. removing <math>\emptyset</math> for overriding <math>\ovl</math> operator)
 
 
 
The rule is added so that it can be applied automatically.  User can choose the rule from the Preferences of the Sequent Prover, so that it can be run as a part of the Automatic Prover or as a part of the Post-Tactic.  The rewriting is carried out to all sub-formulas of the form that match the left-hand side of the rule.
 
 
 
 
 
==Automatically Apply De Morgan's Laws==
 
 
 
The work is related to the following rewriting rules (De Morgan's Laws):
 
 
 
<math>
 
\begin{array}{c}
 
\neg ( P \land \ldots \land Q ) ~~~\mathrel{\widehat{=}}~~~  \neg P \lor \ldots \lor \neg Q \\
 
\neg (P \lor \ldots \lor Q) ~~~\mathrel{\widehat{=}}~~~  \neg P \land \ldots \land \neg Q \\
 
\neg (\forall x \qdot P) ~~~\mathrel{\widehat{=}}~~~  \exists x \qdot \neg P \\
 
\neg (\exists x \qdot P) ~~~\mathrel{\widehat{=}}~~~  \forall x \qdot \neg P
 
\end{array}
 
</math>
 
 
 
Currently, these rewriting rules can be invoked manualy during interactive proofs. The rules is added so that user can choose from the Preferences of the Sequent Prover, so that they can be run as a part of the Automatic Prover or as a part of the Post-Tactic. The rewriting is recursively carried out to all sub-formulas of the form that match the left-hand side of the one of the rule.
 
 
 
==Automatically Rewrite <math>\dom(f) = S</math>==
 
 
 
The work is about rewriting automatically <math>\dom(f) \mathrel{\widehat{=}}  S</math> for selected hypotheses and goal if there is a hypothesis that <math>f</math> is a total function from <math>S</math>, e.g.
 
 
 
<math>
 
\begin{array}{l}
 
f \in S \trel T \\
 
f \in S \tfun T \\
 
f \in S \tinj T \\
 
f \in S \tbij T
 
\end{array}
 
</math>
 
 
 
The rule is added so that it can be applied automatically.  User can choose the rule from the Preferences of the Sequent Prover, so that it can be run as a part of the Automatic Prover or as a part of the Post-Tactic.
 
 
 
==Interactively Rewrite <math>B \subset A</math>==
 
 
 
The work is about providing support for interactively proving <math>B \subset A</math> according to the following rewriting rules.
 
 
 
<math> B \subset A  ~~~\mathrel{\widehat{=}}~~~ B \subseteq A ~\land~ \lnot B = A </math>
 
 
 
The rule has been implemented so that it can be applied both automatically and interactively.
 
 
 
* Automatically: The rule can be chosen from the Preferences of the Sequent Prover to be run as a part of the Automatic Prover or as a part of the Post-Tactic.  The rewriting is carried out to all sub-formulas of the form <math>B \subset A</math>.
 
 
 
* Interactively: The <math>\subset</math> symbol is redden in the formula (either goal or hypotheses) and is applied only to the sub-formula as indicated by the user.
 
 
 
 
 
[[Category:Event-B]]
 
[[Category:Proof]]
 

Revision as of 10:04, 10 September 2009

The purpose is to give more flexibility to tactic providers by allowing them to provide as many tactic applications as they will for a given proof node, even they apply to the same predicate and at the same position.

Proposed Framework

public interface ITacticProvider2 {
   List<ITacticApplication> getPossibleApplications(IUserSupport userSupport,
                                                    IProofTreeNode node,
                                                    Predicate hyp,
                                                    String globalInput);
}


public interface ITacticApplication {
   void apply(String[] inputs, String globalInput, IProgressMonitor monitor);
}


public interface IPositionApplication  extends ITacticApplication {
   Point getHyperlinkBounds();
   String getHyperlinkLabel();
}
public interface IPredicateApplication extends ITacticApplication {
   Image getIcon();
   String getTip();
}