Difference between pages "ADVANCE D3.2 Improvement of automated proof" and "Camille Editor"

From Event-B
(Difference between pages)
Jump to navigationJump to search
imported>Tommy
 
imported>Fabian
(version 0.0.3)
 
Line 1: Line 1:
−
== Overview ==
+
{| align="right"
−
In an Event-B development, more than 60% of the time is spent on proofs. That explains why all users are naturally keen for the proofs to be as automatic as possible and why the automated prover enhancement was a continuous task since the birth of the Rodin platform.
+
| __TOC__
−
This task can be achieved by core platform refactorings and enhancements, such as the addition of integrated reasoners and tactics, but also by the addition of some external reasoning ability such as external provers.<br>
+
|}
−
From the core platform point of view, and within the ten first month of ADVANCE, it consisted into two tasks: the addition of rewriting and inference rules, and the addition of a mechanism to allow the customization and the parametrization or combination of tactics. The user is now able to define various types of tactics called 'profiles' which could be customized and parameterized tactics to discharge some specific proof obligations. The user can furthermore share and backup these defined tactics using the provided import/export mechanism.<br>
+
The first version of the Text Editor will be released in a few weeks, that means in second half of June and not before the Rodin release 1.0 has been published.
−
From an external point of view, the SMT Solvers plug-in allowing to use the SMT solvers within Rodin is an effective alternative to the Atelier-B provers, particularly when reasoning on linear arithmetic. It is maintained in the time frame of ADVANCE, and increases the rate of automatically discharged proof obligations.
 
  
−
== Motivations / Decisions ==
+
Until then we are going to release a few testing releases (beta) for interested users. You will find instructions how to install and use these beta releases on this page.
−
The proportion of automatically discharged proof obligations heavily depends on Auto-Tactic configuration. Sometimes, the automatic prover fails because the tactics are applied in a unappropriate order. Since Rodin 2.4,  a new tactic combinator 'Attempt after Lasso' is available in auto tactic profile editor as well as an import/export feature. Indeed, a user that elaborates a good profile for a certain proof pattern is now able to share or backup this profile thus increasing the number of automatic proofs for a given proof pattern.
 
  
−
Two main reasons mainly motivated the integration of SMT solvers into the Rodin platform. Firstly, to allow Rodin to benefit from the know capacity of such solvers in the field of arithmetics. Secondly, to extract some useful informations from the proofs that these solvers produce such as unsatisfiable cores, in order to significantly decrease the proving time of a modified model. The translation of Event-B language into the SMT-LIB language is the main issue of this integration. Two approaches were developed for this. The more efficient one is based on the translation capabilities of the integrated predicate prover of the Rodin platform (PP). It is completed by translating membership using an uninterpreted predicate symbol, refined with an axiom of the set theory.
 
  
−
== Available Documentation ==
 
−
{{TODO|Fill this paragraph.}}
 
  
−
== Planning ==
+
{| style="width:auto; background-color:#FFFF00; border:2px solid red;  padding:3px;"
−
{{TODO|Fill this paragraph.}}
+
|<b title="Usage warning"><font size="3"> Warning:</font size="3"></b><font size="1">
 +
Don't use the TextEditor yet with your production models!
 +
* The TextEditor is still in development
 +
* It is based on latest SVN Rodin version which uses a changed database model. Therefore its projects cannot be used in older Rodin versions.
  
−
== References ==
+
|}
−
<references/>
 
  
−
[[Category:ADVANCE D3.2 Deliverable]]
+
 
 +
 
 +
==News ==
 +
* ''29th May 2009'': '''Version 0.0.3''' - Fixing first reported bugs. '''Updated strongly recommended.'''
 +
* ''27th May 2009'': '''Version 0.0.2''' - Update the page due to syntax changes and new version on update-site. Announcement on the DEPLOY tooling mailing list.
 +
* ''13th May 2009'': '''Version 0.0.1''' - Creation of this page and publishing the beta update-site for the first time. Presentation at refocus meeting in Southampton.
 +
 
 +
==Installing ==
 +
The TextEditor relies on features of the Rodin release 1.0 which is not yet released. Therefore you will have to create a new Rodin installation. The following steps will guide you through this process:
 +
 
 +
# Download a build of Rodin from our [http://cruise.cs.uni-duesseldorf.de/dashboard/tab/builds CruiseControl server]:
 +
## Point your browser to http://cruise.cs.uni-duesseldorf.de/dashboard/tab/build/detail/org.rodinp.platform
 +
## Download a zip file with a name starting with ''rodin-product'' and matching your platform. For example ''rodin-product-linux.gtk.x86.zip'' if you are working on a Linux system.
 +
# Extract the downloaded zip file.
 +
# Start Rodin from the folder where you extracted the zip file in the previous step.
 +
# Install the TextEditor:
 +
## In the menu choose ''Help'' -> ''Software Updates...''
 +
## Select the tab ''Available Software'' and click ''Add Site...''
 +
## Use the location URL: <tt>http://www.stups.uni-duesseldorf.de/update-beta/</tt>
 +
## Back in ''Available Software'' open the update site you just added
 +
## Select ''Event-B EMF Framework'' and ''Event-B TextEditor'' and click ''Install...''
 +
# Restart Rodin as suggested.
 +
 
 +
 
 +
Now you are ready to use the TextEditor.
 +
 
 +
 
 +
==Updating ==
 +
As often as possible we are going to publish updated beta releases. We recommend that you update your new Rodin installation with these updates for the TextEditor (and EMF Framework).
 +
 
 +
Although we will try to announce these updates on this site too, it is a lot easier if you setup Rodin to let you know when an update is available. The following steps guide you through this process:
 +
 
 +
# In Rodin open the preferences (''Window'' -> ''Preferences'' or for Mac: ''Rodin'' -> ''Preferences'')
 +
# Find ''Install/Update'' -> ''Automatic Updates''
 +
# Select ''Automatically find new updates and notify me''
 +
 
 +
As soon as Rodin finds a new update it will ask you if you would like to install it.
 +
 
 +
 
 +
==Usage ==
 +
This section should help you to get started with the TextEditor.
 +
 
 +
====Opening with the TextEditor ====
 +
At the moment the TextEditor competes with the current graphical Event-B editor when it comes to the selection of a default editor for the double click action to open a model file.
 +
 
 +
Thus from time to time you might experience that an unexpected editor opens. If this happens you can right-click on the model file and select ''Open with TextEditor'' to use the text editor. Usually you should be able to just use a double-click to open a machine or context with the TextEditor.
 +
 
 +
====Syntax ====
 +
The text syntax for machines and contexts is closely related with the pretty-print you might know from the graphical Event-B editor. See the grammar's [[TextEditor_EBNF|EBNF]] for details.
 +
 
 +
As you might notice in the grammar it only describes the structure of machines and contexts. For the terminals ''predicate'', ''expression'' and ''action'' you can use the syntax for formulas which you already know from editing models with the graphical Event-B editor. You can use the ASCII representation of mathematical symbols or their unicode. See the Rodin help for details about the mathematical symbols and their ASCII counterparts.
 +
 
 +
====Editing ====
 +
The TextEditor currently offers the following features:
 +
* ''Syntax error marking'': Syntactical errors are highlighted in the input text.
 +
 
 +
* ''Mathmatical language'': You can type formulas in ASCII syntax and the TextEditor will replace ASCII symbols with their unicode counterparts as soon as you stop typing for a short while.
 +
 
 +
* ''Syntax highlighting'': Keywords (structural and in formulas), labels and comments are highlighted. This happends directly when typing
 +
 
 +
* ''Semantic highlighting'': Identifiers are highlighted based on their semantic meaning, i.e., as variables, constants, parameters, sets, local variables. This highlighting is updated when you stop typing for a short while.
 +
 
 +
* ''Code completion'': The following elements are available for code completion (invoked by Ctrl+Space on the most computers)
 +
** ''Keywords''
 +
** ''Identifiers''
 +
** ''Templates'' (very few so far, please let us know which templates you would like to add)
 +
 
 +
* ''Outline View'': An outline view gives you an overview of the model's structure.
 +
 
 +
* ''Quick Navigation'': The outline view allows clicking on an element to jump to its position within the text.
 +
 
 +
 
 +
Of course the TextEditor offers the common features you know from other text editors, such as: copy, paste, moving of text (try Alt+Up or Alt+Down), undo, redo, ...
 +
 
 +
====Restrictions ====
 +
Due to some design decisions and its combination with the Rodin platform the TextEditor comes with a few restrictions:
 +
* Semantic analysis (for highlighting and code completion for example) can only performed if the overall structure of the input is parsable. Therefore you might experience situtions when the semantic highlighting or the code completion produces unexpected results because it is based on outdated parsing information.
 +
 
 +
* Parsing for formulas, i.e., predicates, actions and expressions can only be performed if the overall structure of the input is parsable. If the structure is not parsable ascii symbols will not be replaced until you correct the overall structure.
 +
 
 +
* Also see the [[TextEditor_EBNF|EBNF page]] for some restrictions in the syntax.
 +
 
 +
 
 +
==Bugs and Features ==
 +
Please use this section to report any bugs you find and let us know about features you would like to see in the TextEditor.
 +
 
 +
Regarding feature requests: Any feature request is welcome! But please keep in mind that we are preparing for a first stable release of the TextEditor. So we might not start working on your feature request in the next weeks. ''The focus until the first release is on stability!''
 +
 
 +
 
 +
====Bugs ====
 +
* ''please add it when you fine one''
 +
 
 +
====Feature Requests ====
 +
* Make TextEditor an [http://en.wikipedia.org/wiki/Eierlegende_Wollmilchsau Eierlegende Wollmilchsau]... ;-)
 +
 
 +
====Comments ====
 +
Of course any other feedback is welcome too! We appreciate when you let us now what you think about the TextEditor.

Revision as of 06:20, 29 May 2009

The first version of the Text Editor will be released in a few weeks, that means in second half of June and not before the Rodin release 1.0 has been published.

Until then we are going to release a few testing releases (beta) for interested users. You will find instructions how to install and use these beta releases on this page.


Warning:

Don't use the TextEditor yet with your production models!

  • The TextEditor is still in development
  • It is based on latest SVN Rodin version which uses a changed database model. Therefore its projects cannot be used in older Rodin versions.


News

  • 29th May 2009: Version 0.0.3 - Fixing first reported bugs. Updated strongly recommended.
  • 27th May 2009: Version 0.0.2 - Update the page due to syntax changes and new version on update-site. Announcement on the DEPLOY tooling mailing list.
  • 13th May 2009: Version 0.0.1 - Creation of this page and publishing the beta update-site for the first time. Presentation at refocus meeting in Southampton.

Installing

The TextEditor relies on features of the Rodin release 1.0 which is not yet released. Therefore you will have to create a new Rodin installation. The following steps will guide you through this process:

  1. Download a build of Rodin from our CruiseControl server:
    1. Point your browser to http://cruise.cs.uni-duesseldorf.de/dashboard/tab/build/detail/org.rodinp.platform
    2. Download a zip file with a name starting with rodin-product and matching your platform. For example rodin-product-linux.gtk.x86.zip if you are working on a Linux system.
  2. Extract the downloaded zip file.
  3. Start Rodin from the folder where you extracted the zip file in the previous step.
  4. Install the TextEditor:
    1. In the menu choose Help -> Software Updates...
    2. Select the tab Available Software and click Add Site...
    3. Use the location URL: http://www.stups.uni-duesseldorf.de/update-beta/
    4. Back in Available Software open the update site you just added
    5. Select Event-B EMF Framework and Event-B TextEditor and click Install...
  5. Restart Rodin as suggested.


Now you are ready to use the TextEditor.


Updating

As often as possible we are going to publish updated beta releases. We recommend that you update your new Rodin installation with these updates for the TextEditor (and EMF Framework).

Although we will try to announce these updates on this site too, it is a lot easier if you setup Rodin to let you know when an update is available. The following steps guide you through this process:

  1. In Rodin open the preferences (Window -> Preferences or for Mac: Rodin -> Preferences)
  2. Find Install/Update -> Automatic Updates
  3. Select Automatically find new updates and notify me

As soon as Rodin finds a new update it will ask you if you would like to install it.


Usage

This section should help you to get started with the TextEditor.

Opening with the TextEditor

At the moment the TextEditor competes with the current graphical Event-B editor when it comes to the selection of a default editor for the double click action to open a model file.

Thus from time to time you might experience that an unexpected editor opens. If this happens you can right-click on the model file and select Open with TextEditor to use the text editor. Usually you should be able to just use a double-click to open a machine or context with the TextEditor.

Syntax

The text syntax for machines and contexts is closely related with the pretty-print you might know from the graphical Event-B editor. See the grammar's EBNF for details.

As you might notice in the grammar it only describes the structure of machines and contexts. For the terminals predicate, expression and action you can use the syntax for formulas which you already know from editing models with the graphical Event-B editor. You can use the ASCII representation of mathematical symbols or their unicode. See the Rodin help for details about the mathematical symbols and their ASCII counterparts.

Editing

The TextEditor currently offers the following features:

  • Syntax error marking: Syntactical errors are highlighted in the input text.
  • Mathmatical language: You can type formulas in ASCII syntax and the TextEditor will replace ASCII symbols with their unicode counterparts as soon as you stop typing for a short while.
  • Syntax highlighting: Keywords (structural and in formulas), labels and comments are highlighted. This happends directly when typing
  • Semantic highlighting: Identifiers are highlighted based on their semantic meaning, i.e., as variables, constants, parameters, sets, local variables. This highlighting is updated when you stop typing for a short while.
  • Code completion: The following elements are available for code completion (invoked by Ctrl+Space on the most computers)
    • Keywords
    • Identifiers
    • Templates (very few so far, please let us know which templates you would like to add)
  • Outline View: An outline view gives you an overview of the model's structure.
  • Quick Navigation: The outline view allows clicking on an element to jump to its position within the text.


Of course the TextEditor offers the common features you know from other text editors, such as: copy, paste, moving of text (try Alt+Up or Alt+Down), undo, redo, ...

Restrictions

Due to some design decisions and its combination with the Rodin platform the TextEditor comes with a few restrictions:

  • Semantic analysis (for highlighting and code completion for example) can only performed if the overall structure of the input is parsable. Therefore you might experience situtions when the semantic highlighting or the code completion produces unexpected results because it is based on outdated parsing information.
  • Parsing for formulas, i.e., predicates, actions and expressions can only be performed if the overall structure of the input is parsable. If the structure is not parsable ascii symbols will not be replaced until you correct the overall structure.
  • Also see the EBNF page for some restrictions in the syntax.


Bugs and Features

Please use this section to report any bugs you find and let us know about features you would like to see in the TextEditor.

Regarding feature requests: Any feature request is welcome! But please keep in mind that we are preparing for a first stable release of the TextEditor. So we might not start working on your feature request in the next weeks. The focus until the first release is on stability!


Bugs

  • please add it when you fine one

Feature Requests

Comments

Of course any other feedback is welcome too! We appreciate when you let us now what you think about the TextEditor.

Retrieved from ‘https://wiki.event-b.org/index.php?title=ADVANCE_D3.2_Improvement_of_automated_proof&oldid=1094’