|
|
| (One intermediate revision by one other user not shown) |
| Line 1: |
Line 1: |
| == General ==
| | [http://handbook.event-b.org/current/html/faq.html Rodin Handbook (FAQ)] |
| === What is event-B? ===
| |
| '''Event-B''' is a formal method for system-level modelling and analysis. Key features of event-B are the use of set theory as a modelling notation, the use of refinement to represent systems at different abstraction levels and the use of mathematical proof to verify consistency between refinement levels. More details are available in http://www.event-b.org/
| |
| | |
| === What is the difference between event-B and the B method? ===
| |
| | |
| Event-B is derived from the [http://en.wikipedia.org/wiki/B-Method B method]. Both notations have the same [http://en.wikipedia.org/wiki/Jean-Raymond_Abrial inventor], and share many common concepts (set-theory, refinement, proof obligations, ...) However, they are used for quite different purpose. The B method is devoted to the development of ''correct by construction'' software, while the purpose of event-B is to model full systems (including hardware, software and environment of operation).
| |
| | |
| Both notations use a mathematical language which are quite close but do not match exactly (in particular, operator precedences are different).
| |
| | |
| === What is Rodin? ===
| |
| The '''Rodin Platform''' is an Eclipse-based IDE for Event-B that provides effective support for refinement and mathematical proof. The platform is open source, contributes to the Eclipse framework and is further extendable with plugins.
| |
| | |
| === Where does the ''Rodin'' name come from? ===
| |
| | |
| The Rodin platform was initially developed within the European Commission funded Rodin project (IST-511599 ), where Rodin is an acronym for "Rigorous Open Development Environment for Complex Systems” . Rodin is also the name of a famous French [http://en.wikipedia.org/wiki/Auguste_Rodin sculptor], one of his most famous work being the [http://en.wikipedia.org/wiki/The_Thinker Thinker].
| |
| | |
| == General Tool Usage ==
| |
| | |
| === Do I lose my proofs when I clean a project ? ===
| |
| | |
| No ! This is a common misunderstanding of what a project clean does. A project contains two kinds of files:
| |
| * those you can edit: contexts, machines, proofs
| |
| * those generated by a project build: proof obligations, proof statuses (roughly speaking, for each proof obligation, ''discharged'' or ''not discharged'')
| |
| | |
| The cleaner just undoes what the builder does, i.e. it removes proof obligations and statuses, but it never modifies any proof.
| |
| | |
| A status may change from ''discharged'' to ''not discharged'' when the proof is no more compatible with the corresponding proof obligation (because hypotheses changed for instance), but '''the proof itself is still there !''' You can try to [[Proof_Obligation_Commands#Proof_Replay_on_Undischarged_POs|replay]] it.
| |
| | |
| A confusion might arise from the possibility to launch automatic provers upon build. The cleaner does not undo these automatic proofs (why would it ?!!). Once a proof is made, the platform does not modify or delete it by itself. Even [[Proof Purger Interface#Why proofs become obsolete | obsolete proofs]] are preserved !
| |
| | |
| === How do I install external plug-ins without using Eclipse Update Manager? ===
| |
| Although it is preferred to install additional plug-ins into the Rodin platform using the Update Manager of Eclipse, this might not always be practical. In this case, a manner to install these plug-ins is to emulate either manually or using ad-hoc scripts the operations normally performed by the Update Manager.
| |
| | |
| This manual installation of plug-ins is described in ''[[Installing external plug-ins manually]]''.
| |
| | |
| === The builder takes too long ===
| |
| Generally, the builder spends most of its time attempting to prove POs. There are basically two ways to get it out of the way:
| |
| * the first one is to disable the automated prover in the Preferences panel.
| |
| * the second one is to mark some PO as reviewed when you don't want the auto-prover to attempt them anymore.
| |
| Note that if you disable the automated prover, you always can run it later on some files by using the contextual menu in the event-B Explorer.
| |
| | |
| To disable the automated prover, open Rodin <tt>Preferences</tt> (menu {{menu|Window > Preferences...}}). In the tree in the left-hand panel, select {{menu|Event-B > Sequent Prover > Auto-tactic}}. Then, in the right-hand panel ensure that the checkbox labelled <tt>Enable auto-tactic for proving</tt> is disabled.
| |
| | |
| To review a proof obligation, just open it in the interactive prover, then click on the ''review'' button (this is a round blue button with a ''R'' in the proof control toolbar). The proof obligation should now labelled with the same icon in the event-B explorer.
| |
| | |
| ===What are the ASCII shortcuts for mathematical operators===
| |
| | |
| The ASCII shortcuts that can be used for entering mathematical operators are described in the help of the Rodin keyboard plug-in. In the help system, this page has the following path {{menu|Rodin Keyboard User Guide > Getting Started > Special Combos}}.
| |
| | |
| This page is also available in the dynamic help system. The advantage of using dynamic help is that it allows to display the help page side-by-side with the other views and editors. To start the dynamic help, click {{menu|Help > Dynamic Help}}, then click {{menu|All Topics}} and select the page in the tree.
| |
| | |
| ===Rodin (and eclipse) doesn't take into account the MOZILLA_FIVE_HOME environment variable===
| |
| You have to add a properties by appending the following code to your {{file|eclipse/eclipse.ini}} or {{file|rodin/rodin.ini}} file:
| |
| -Dorg.eclipse.swt.browser.XULRunnerPath=/usr/lib/xulrunner/xulrunner-xxx
| |
| | |
| === No More Handles ===
| |
| | |
| On Windows platforms, it may happen that Rodin crashes, complaining about "no more handles". This is an OS specific limitation, described [http://journals.jevon.org/users/jevon-phd/entry/19833 here] and [https://bugs.eclipse.org/bugs/show_bug.cgi?id=211124 there]. A workaround is provided in [http://blogs.msdn.com/b/ntdebugging/archive/2007/01/04/desktop-heap-overview.aspx this site].
| |
| | |
| === Software installation fails ===
| |
| | |
| When installing softwares from update sites (Help > Install New Software...) it sometimes fails with an error saying something like:
| |
| | |
| No repository found containing: osgi.bundle,org.eclipse.emf.compare,1.0.1.v200909161031
| |
| No repository found containing: osgi.bundle,org.eclipse.emf.compare.diff,1.0.1.v200909161031
| |
| ...
| |
| | |
| This is an eclipse/p2 bug, referenced [http://stackoverflow.com/questions/511367/error-when-updating-eclipse here].
| |
| | |
| The workaround is to:
| |
| * go to Window > Preferences > Install/Update > Available Software Sites
| |
| * sites then add them back again, which can be achieved in the "Available Software Sites" preference page by:
| |
| * select all update sites (by highlighting them all those that are checked)
| |
| * Export them
| |
| * Remove them
| |
| * restart Rodin
| |
| * go back to the preference page and import update sites back (from the previously exported file)
| |
| | |
| == Modeling ==
| |
| === Witness for {{Ident|Xyz}} missing. Default witness generated ===
| |
| A parameter as disappeared during a refinement. If this is intentional, you have to add a [[Witnesses (Modelling Language)|witness]] telling how the abstract parameter is refined.
| |
| | |
| === Identifier {{ident|Xyz}} should not occur free in a witness ===
| |
| You refer to {{ident|Xyz}} in a witness predicate where {{ident|Xyz}} is a disappearing abstract variable or parameter which is not set as the witness label.
| |
| | |
| === In {{event|INITIALISATION}}, I get ''Witness {{ident|Xyz}} must be a disappearing abstract variable or parameter'' ===
| |
| The witness is for the after value of the abstract variable, hence you should use the primed variable. The witness label should be {{ident|Xyz'}}, and the predicate should refer to {{ident|Xyz'}} too.
| |
| | |
| === I've added a witness for {{ident|Xyz}} but it keeps saying ''"Identifier {{ident|Xyz}} has not been defined"'' ===
| |
| As specified in the [[Witnesses (Modelling Language)|modelling language manual]], the witness must be labelled by the name {{Ident|Xyz}} of the concrete variable being concerned.
| |
| | |
| === What are type expressions in Event-B? ===
| |
| The type expressions are defined recursively as follows:
| |
| | |
| * Built-in types: ℤ, BOOL (Note that ℕ is NOT a type expressions).
| |
| | |
| * Any carrier set is a type expression.
| |
| | |
| * If <math>T</math> is a type expression then <math>ℙ(T)</math> is a type expression.
| |
| | |
| * If <math>S</math> and <math>T</math> are type expressions then <math>S × T</math> is a type expression.
| |
| | |
| == Proving ==
| |
| | |
| === How can I do a Proof by Induction? ===
| |
| [[Induction proof|This page about proof by induction]] will give you some starting tips.
| |
| | |
| === Labels of proof tree nodes explained ===
| |
| * {{ident|ah}} means ''add hypothesis'',
| |
| * {{ident|eh}} means rewrite with ''equality from hypothesis'' from left to right,
| |
| * {{ident|he}} means rewrite with ''equality from hypothesis'' from right to left,
| |
| * {{ident|rv}} tell us that this goal as been manually [[The_Proving_Perspective_(Rodin_User_Manual)#The_Proof_Control_Window|reviewed]],
| |
| * {{ident|sl/ds}} means ''selection/deselection'',
| |
| * {{ident|PP}} means ''discharged by the predicate prover''
| |
| * {{ident|ML}} means ''discharged by the mono lemma prover''
| |
| | |
| == How to contribute and develop ? ==
| |
| See the [[Developer FAQ]] page.
| |
| | |
| [[Category:User FAQ]]
| |
