Difference between pages "Tasking Event-B Tutorial" and "Theory Release History"

From Event-B
(Difference between pages)
Jump to navigationJump to search
imported>Andy
 
 
Line 1: Line 1:
THIS PAGE IS UNDER CONSTRUCTION !!!!!!
+
Back to [[Theory Plug-in]].
  
For more information contact Andy Edmunds - University of Southampton - mailto:ae2@ecs.soton.ac.uk
+
Follow this page for the latest on the Theory plug-in. The user manual is also provided together with the installation details.
=== Tasking Event-B Tutorial Overview ===
 
  
This code generation tutorial supplements the Heating Controller tutorial example, and makes use of example projects from the download site. The code generation stage produces implementable Ada code, and also an Event-B project which models the implementation. The Ada code is produced using a pretty printer tool from an intermediate model, the Common Language model (IL1), generated by a translation tool. An overview of Tasking Event-B can be found on the [[Tasking_Event-B_Overview]] page.
+
===News===
 +
* ''22th December 2020'': [[#Version_4.0.1|Version 4.0.1]] is released. It requires Rodin 3.5.
 +
* ''19th December 2014'': [[#Version_3.0.0|Version 3.0.o]] is released. It requires Rodin 3.1.
 +
* ''10th July 2014'': [[#Version_2.0.2|Version 2.0.2]] is released. It requires Rodin 2.8.
 +
* ''24th June 2014'': [[#Version_2.0.1|Version 2.0.1]] is released. It requires Rodin 2.8.
 +
* ''30th April 2014'': [[#Version_2.0.0|Version 2.0.0]] is released. It requires Rodin 2.8. This release contains major changes in the features and accessibilities.
 +
* ''20th April 2012'': [[#Version_1.3.2|Version 1.3.2]] is released. It requires Rodin 2.4.
 +
* ''15th August 2011'': [[#Version_1.2|Version 1.2]] is released. It requires Rodin 2.2.2.
 +
* ''6th August 2011'': [[#Version_1.1|Version 1.1]] is released. It requires Rodin 2.2.2.
 +
* ''8th July 2011'': [[#Version_1.0|Version 1.0]] is released. It requires Rodin 2.2.
 +
* ''22nd May 2011'': [[#Version_0.8|Version 0.8]] released. It is based on Rodin 2.1.1.
 +
* ''11th April 2011'': [[#Version_0.7|Version 0.7]] released. It is based on Rodin 2.1.1.
 +
* ''6th January 2011'': [[#Version_0.6|Version 0.6]] released. It is based on Rodin 2.0.1.
 +
* ''28th October 2010'': [[#Version_0.5|Version 0.5]] released. It is based on Rodin 2.0.
  
The Heating Controller development has been refined to the point where we wish to add implementation constructs. The Event-B language is not expressive enough to fully describe the implementation. Tasking Event-B facilitates this final step to implementation, by extending Event-B with the necessary constructs. Event-B machines that are to be implemented (and their seen Contexts) are selected and added to a ''Tasking Development''; the Tasking Development files have the file extension ''.tasking''. The machines in the Tasking Development are then extended with implementation details.
+
===Releases===
 +
===== Version 4.0.1 =====
 +
''22th December 2020''
  
The example/tutorial projects are,
+
Release target: Rodin 3.5
 +
* Bug fixes:
 +
** The theory plugin now takes into account updates in theories, as well as creating a theory after using it (there was a cache issue).
 +
** The error messages at launch about rule-based provers failing to find the context of the proof have been removed.
 +
** The dropdown list in theory imports is now usable (there was an off-by-one issue when selecting an element in the list).
 +
** Manually applying an inference rule no longer throws a NullPointerException.
 +
** It is now possible to rename theories.
 +
** The TheoryPath creation dialog box has been simplified.
 +
* Optimizations:
 +
** The proving interface is now much more responsive, even when a theory contains a lot of rewrite rules (we have implemented a cache of the places where a rewrite rule can apply).
 +
** The theory plugin now generates much simpler WD conditions, especially for the pred, succ, prj1, prj2, and id operators.
  
{| border="1"
+
===== Version 4.0.0-RC1 =====
|Heating_ControllerTutorial_Completed
+
''10th April 2017''
|An example project with a completed Tasking Development and IL1 model (post IL1 translation, but before Event-B translation).
 
|-
 
|Heating_ControllerTutorial_Completed_Gen
 
|Same as the example project above, but with Event-B model translations. The difference being that this development includes a model of the implementation. These are refinements that include a program counter to describe flow of execution in each task.
 
|-
 
|Heating_ControllerTutorial_Step1
 
|A bare project for step 1 of the [[Code_Generation_Tutorial#The_Tutorial |tutorial]].
 
|-
 
|Heating_ControllerTutorial_Step2
 
|A partially completed tasking development for steps 2, 3 and 4 of the [[Code_Generation_Tutorial#The_Tutorial |tutorial]].
 
|}
 
  
== Preliminaries ==
+
Release target: Rodin 3.2
Before further discussion of the modelling aspects, we take a look at the PrettyPrint viewers. The PrettyPrinters make the viewing of IL1 and tasking models easier; it also provides a route to generate source code. The source code can easily be pasted from the IL1 Pretty Printer window into an the Ada source file .  
+
* AST Extensions (4.0.0) Major API change.
==== The PrettyPrint View of a Tasking Development ====
+
** Compatibility upgrade to Rodin 3.2
To open the Tasking PrettyPrint viewer,
+
** Support for get operator position for INFIX extended predicate operators.
* from the top-menu select ''Window/Show View/Other/Tasking Pretty Printer''.
+
** Improve pattern matching for associative operators.
 +
* Theory plug-in Branding (0.0.1) Initial version
 +
* Theory Core (4.0.0) Internal implementation changes.
 +
** Compatibility upgrade to Rodin 3.2
 +
** Support for INFIX extended predicate operators.
 +
** Various bugs fixed.
 +
* Theory help (2.0.0) User documentations.
 +
* Theory Keyboard (0.0.1) Initial version (A special plug-in for typesetting Theory).
 +
** Support for typesetting Real arithmetics (plus, unary minus, multiply, divide, less than, less than or equal, greater than, greater than or equal).
 +
* Theory Rule-based Prover (4.0.0)
 +
** Reasoners' input does not contain the proof-obligation context.
 +
** Use the current sequent's origin to get the proof-obligation context.
 +
** Bug fixed: translate formula to ensure they have the same formula factory.
 +
** Added version numbers for reasoners.
 +
** Automatic rewrite and inference tactics are re-implemented so that each rule application is visible in proof trees.
 +
* Theory UI (3.0.0)
  
Note that the Tasking PrettyPrinter may have to be closed when editing the Tasking Development, since it can give rise to exceptions. The PrettyPrinter would need further work to make it robust, however it is intended only as a short-term solution.
+
===== Version 3.0.0 =====
 +
''17th December 2014''
  
* Open the ''Heating_ControllerTutorial_Completed'' Project and switch to the Resource Perspective.
+
Release target : Rodin 3.1
* Open the ''.tasking'' model and inspect it. Clicking on the Main, Machine or Event nodes updates the pretty print window.
+
* migration changes to Rodin 3.1
  
==== Viewing Source Code ====
+
===== Version 2.0.2 =====
aka. The PrettyPrint View of an IL1 Model.
+
''10th July 2014''
  
To view Ada source code,
+
Release target : Rodin 2.8
* from the top-menu select ''Window/Show View/Other/IL1 Pretty Printer''.
+
* bug fixes.  
* Open the ''Heating_ControllerTutorial_Completed'' Project and switch to the Resource Perspective.
 
* Open the ''.il1'' model and inspect it. Clicking on the Protected, Main Entry, or Task nodes updates the pretty print window.
 
  
==== Cleaning the Tasking Development ====
+
===== Version 2.0.1 =====
If the ''.tasking'' file has errors, then it may need cleaning. To do this right-click on the ''Main'' node, select ''Epsilon Translation/CleanUp''. If a model has errors it can still be viewed by clicking on the ''Selection'' tab at the bottom of the tasking editor window.
+
''24th June 2014''
  
== Using the Tasking Extension ==
+
Release target : Rodin 2.8
The steps needed to generate code from an Event-B model, in this tutorial, are as follows,
+
* bug fixes.  
* Step 1 - [[Tasking Event-B_Tutorial#Creating The Tasking Development|Create the tasking development]].
 
* Step 2 - [[Tasking Event-B_Tutorial#Providing the Annotations for Implementations|Add Tasking annotations]].
 
* Step 3 - [[Tasking Event-B_Tutorial#Optional Annotations for Addressed Variables|Add annotations for addressed variables (optional)]].
 
* Step 4 - [[Tasking Event-B_Tutorial#Invoking the Translation|Invoke translators]].
 
  
==== Creating The Tasking Development ====
+
===== Version 2.0.0 =====
* Change to the Event-B Perspective.
+
''30th April 2014''
* Open the ''Heating_ControllerTutorial_Step1'' Project.
 
* Select the following Machines: Display_Update_Task1, Envir1, Heater_Monitor_Task1, Shared_Object1, Temp_Ctrl_Task1 and HC_CONTEXT.
 
* Right-click and select ''Make Tasking Development/Generate Tasking Development''.
 
  
The new Tasking Development will not be visible in the Event-B perspective, change to the resource perspective, open and inspect the new ''.tasking'' file. The Tasking Development contains (the EMF representation of) the machines that we wish to provide implementations for. In order to introduce the new concepts we have prepared a partially complete development.  
+
Release target : Rodin 2.8
 +
* Major changes in the usability.
 +
* Important bug fixes.  
  
* Change the tasking development, if necessary, so that the machine that models the environment is at the top of the tree of machines.
+
===== Version 1.3.2 =====
 +
''20th April 2012''
  
In the simulation implementation, elements of the Environ machine must be declared first.
+
Release target : Rodin 2.4
 +
* Important bug fixes.
 +
* Improvement of deployment and un-deployment wizards
  
Change to the Project ''Heating_ControllerTutorial_Step2'' to begin the next step.
+
===== Version 1.2 =====
 +
''15th August 2011''
  
==== Providing the Annotations for Implementations ====
+
Release target : Rodin 2.2.2
* Close any Tasking Pretty Print Viewers that remain open. The incomplete model will give rise to exceptions.
+
* Bug fixes.  
* Go to the to the Resource Perspective.
+
* Added capability to instantiate multiple theorems at once.
* Open and inspect the ''.tasking'' machine.
+
* Added automatic tactic for expanding operator definitions RbPxd·
  
The ''Temp_Ctrl_Task1Impl'', ''Envir1'' and ''Shared_Object1'' machines are incomplete. We will take the necessary steps to provide implementation details.
+
===== Version 1.1 =====
 +
''6th August 2011''
  
===== The Temp_Ctrl_Task1Impl Machine =====
+
Release target : Rodin 2.2.2
In the partially complete tutorial project we have already identified the ''Temp_Ctrl_Task1Impl'' as an ''Auto Task'' Tasking Machine, by adding the ''Auto Task'' extension. ''Auto Tasks'' are tasks that will be declared and defined in the ''Main'' procedure of the implementation. The effect of this is that the ''Auto Tasks'' are created when the program first loads, and then activated (made ready to run) before the ''Main'' procedure body runs. We have added the ''Periodic Task'' extension to the ''Auto Task'', and set a period of 250 milliseconds. We have provided a PrettyPrint view of the completed [http://wiki.event-b.org/images/Temp_Ctrl_Task1Impl.pdf Temp_Ctrl_Task1Impl] that can be read in conjunction with the tutorial.
+
* Theory library first version.  
 +
* Bug fixes.  
 +
* Improved UI.
  
We will now complete the sequence that has been partially defined in the task body.
+
===== Version 1.0 =====
 +
''8th July 2011''
  
*'''Add Sensing between TCSense_Temperatures and ENSense_Temperatures'''.
+
Release target : Rodin 2.2
** Expand the Temp_Ctrl_Task1Impl ''Auto Task Machine'' node.
 
** Expand the ''Seq'' sub-tree.
 
** Right-click on the ''Seq'' node and select ''New Child/Left Branch EventWrapper''.
 
** Provide the event label ''tc1'' using the properties view.
 
** Right-click on Event Wrapper and select ''New Child/ Synch Events''.
 
** Select ''Synch Events'' and go to the drop-down menu of the ''Local Event'' property.
 
** At this point the drop-down box displays a number of event names, select the '''second''' ''TCSense_Temperatures'' event.
 
** Go to the drop-down menu of the ''Remote Event'' property.
 
** From the list of events select the '''first''' ''ENSense_Temperatures'' event.
 
  
By relating the sensing events in this way we describe a simulation of the interaction between the task and environment. The details of the interaction are embodied in the events themselves. This is implemented in the simulation code as a write to environment variables using a subroutine call.  
+
* Bug fixes.
 +
* Added import relationships between theories.  
 +
* Added experimental support for recursive definitions.
 +
* Improved project as well as workspace scope for mathematical and prover extensions.
 +
* Added tactic (xd) to expand all definitions.
 +
* Fixed support for polymorphic theorems.
  
Note that the Synch Events construct is used in several ways. We use it to implement [[Tasking Event-B Overview#Control Constructs|Event Synchronisation]]; sensing and actuation; and as a simple event wrapper. An example of its use in a simple event wrapper follows. The simple event wrapper is used to update local state; there is no synchronisation, as such, but we re-use the constructs that already exist rather than create new ones. We now add a wrapped event to the sequence:
+
===== Version 0.8 =====
 +
''22nd May 2011''
  
*'''Add the Wrapped Event TCCalculate_Average_Temperature'''.
+
Release target : Rodin 2.1.1
** Expand the sub-tree of the second ''Seq'' node.
 
** Right-click on the ''Seq'' node and select ''New Child/Left Branch EventWrapper''.
 
** Provide the event label ''tc2'' using the properties view.
 
** Right-click on Event Wrapper and select ''New Child/ Synch Events''.
 
** Select ''Synch Events'' and go to the drop-down menu of the ''Local Event'' property.
 
** From the list of events select the ''TCCalculate_Average_Temperature'' event.
 
  
The addition of the wrapped event, to the sequence, is simply specification of event ordering. It is implemented in code as a sequential subroutine call statement. We now specify event synchronisation between the task and shared object:
+
* Bug fixes.  
 +
* Added import relationships between theories.
 +
* Added experimental support for recursive definitions.
 +
* Added project as well as workspace scope for mathematical and prover extensions.
  
*'''Add Synchronisation between TCGet_Target_Temperature2 and SOGet_Target_Temperature2'''.
+
===== Version 0.7 =====
** Further expand the ''Seq'' sub-tree until Eventwrapper tc3 appears.
+
''11th April 2011''
** Right-click on the sibling ''Seq'' node (lowest in the tree) and select ''New Child/Left Branch EventWrapper''.
 
** Provide the event label ''tc4'' using the properties view.
 
** Right-click on Event Wrapper and select ''New Child/ Synch Events''.
 
** Select ''Synch Events'' and go to the drop-down menu of the ''Local Event'' property.
 
** At this point the drop-down box displays a number of event names, select the '''second''' ''TCGet_Target_Temperature2'' event.
 
** Go to the drop-down menu of the ''Remote Event'' property.
 
** From the list of events select the '''second''' ''SOGet_Target_Temperature2'' event.
 
  
We have now completed the task body, and next provide additional details for events. In the first instance we focus on the the ''TCGet_Target_Temperature2 '' event in ''Temp_Ctrl_Task1Impl'' which is to be synchronized with the ''SOGet_Target_Temperature2 '' event in ''Shared_Object1Impl''.  
+
Bug fixes. Fixed for Rodin 2.1.1.
  
*'''Add The Event Synchronisation Extension'''.
+
===== Version 0.6 =====
** Right-click on the ''TCGet_Target_Temperature2'' Event node.
+
''6th January 2011''
** Select ''New Child/Implementation'' from the menu.
 
** Go to the Implementation properties view and set the ''Implementation Type'' property to ''ProcedureSynch''.
 
  
We have identified the event as one that partakes in a synchronisation.
+
Minor bug fixes and improvements to theories pretty printer.
  
*'''Identify a parameter direction'''.
+
===== Version 0.5 =====
** Right-click on the ''tm'' node.
+
''28th October 2010''
** Select''New Child/Parameter Type''.
 
** Go to the ''Parameter Type'' properties view and set the ''Parameter Type'' property to ''actualIn''.
 
  
We have now identified the parameter as an actualIn (this models a call's return value).
+
This is the first release of the Theory plug-in with support for mathematical as well as prover extensions.
  
Next we look at the sensing event ''TCSense_Temperatures'' event in ''Temp_Ctrl_Task1Impl''. Sensing (and actuating) can be viewed as a kind of synchronisation. The simulation code has a subroutine corresponding to the ''ENSense_Temperatures'' event in the Environ machine ''Envir1Impl'':
+
===Features Requests and Bugs===
 
+
Please do not hesitate to raise any issues with regards to usability as well as efficiency. Finally, please remember to report any bugs through the SourceForge portal.
*'''Add The Sensed Event Extension'''.
 
** Right-click on the ''TCSense_Temperatures'' Event node.
 
** Select ''New Child/Implementation'' from the menu.
 
** Go to the Implementation properties view and set the ''Implementation Type'' property to ''Sensing''.
 
 
 
We have identified the event as a sensing event. Now we add the parameter direction:
 
 
 
*'''Identify parameter directions'''.
 
** Right-click on the ''t1'' node.
 
** Select''New Child/Parameter Type''.
 
** Go to the ''Parameter Type'' properties view and set the ''Parameter Type'' property to ''actualIn''.
 
** Right-click on the ''t2'' node.
 
** Select''New Child/Parameter Type''.
 
** Go to the ''Parameter Type'' properties view and set the ''Parameter Type'' property to ''actualIn''.
 
 
 
We have now identified the parameters as an actualIn (modelling a simulation's subroutine call return value).
 
 
 
===== The Shared Machine =====
 
 
 
The next step is to identify the ''Shared_Object1Impl'' machine as a ''Shared Machine''. A PrettyPrint view of the [http://wiki.event-b.org/images/Shared_Object1Impl.pdf Shared_Object1Impl] shared machine can be read in conjunction with the text. The ''Shared_Object1Impl'' Machine will be extended using the Event-B extension mechanism.
 
* Right-click on the ''Shared_Object'' Machine node in the ''.tasking'' file.
 
* Select ''New Child/Shared Machine'' from the menu.
 
 
 
We now show how to extend the ''SOGet_Target_Temperature2'' event of the Shared Machine with details about its implementation. The ''SOGet_Target_Temperature2'' event in ''Shared_Object1Impl'' synchronizes with the ''TCGet_Target_Temperature2'' event in the '' Temp_Ctrl_Task1Impl''.
 
 
 
* '''Identify SOGet_Target_Temperature2 as a Synchronized event'''.
 
** Right-click on the ''SOGet_Target_Temperature2 '' Event node.
 
** Select ''New Child/Implementation'' from the menu.
 
** Go to the Implementation properties view and set the ''Implementation Type'' property to ''ProcedureSynch''.
 
 
 
* '''Identify the outgoing (return) parameter'''.
 
** Right-click on the ''tm'' node.
 
** Select ''New Child/Parameter Type''.
 
** Go to the ''Parameter Type'' properties view and set the ''Parameter Type'' property to ''formalOut''.
 
 
 
===== The Environ Machine =====
 
In the prepared machine we have identified the ''Envir1Impl'' as an ''Environ Machine'', by adding the ''Environ Machine'' extension. ''Envir1Impl'' models a task that simulates the environment, and can be used to generate simulation code. For deployment in a non-simulated environment the environ machine's generated code can be ignored; we provide details of non-simulated code using addressed variables later. As before, a [http://wiki.event-b.org/images/Envir1Impl_2.pdf PrettyPrint] view is available. We have added the ''Periodic Task'' extension to the ''Auto Task'', and set a period of 100 milliseconds.
 
 
We will now complete the sequence that has been partially defined in the task body. The following specification models simulation of a temperature change; the temperature value is represented by a monitored variable in the environment. The generated code simulates the temperature change in the environment by changing the monitored value. 
 
 
 
*'''Model Temperature Change in the environment'''.
 
** Expand the Environ1Impl ''Environ Machine'' node.
 
** Expand the ''Seq'' sub-tree fully.
 
** Right-click on the last ''Seq'' node in the tree and and select ''New Child/Left Branch EventWrapper''.
 
** Provide the event label ''e4'' using the properties view.
 
** Right-click on Event Wrapper and select ''New Child/ Synch Events''.
 
** Select ''Synch Events'' and go to the drop-down menu of the ''Local Event'' property.
 
** At this point the drop-down box displays a number of event names, select the '''first''' ''ENAlter_Temperature_Sensor1'' event.
 
 
 
Output to the screen during the simulation can be specified as follows:
 
 
 
*'''Text Output during Simulation.'''.
 
** Right-click on the last ''Seq'' node in the tree and and select ''New Child/Right Branch Output''.
 
** Select the ''Output'' node, and in the properties menu select the ''Element'' property drop down box.
 
** Select the ''last'' variable ''ctd'' that appears in the list.
 
** In the ''Text'' property field, add a textual description to accompany the text output.
 
 
 
The generated code will print the text, and the value of the variable, to the screen. The next step is to identify the ''ENAlter_Temperature_Sensor1'' as a ''ProcedureDef''.
 
 
 
* '''Identify ENAlter_Temperature_Sensor1 as a ProcedureDef event'''.
 
** Right-click on the ''ENAlter_Temperature_Sensor1'' Event node.
 
** Select ''New Child/Implementation'' from the menu.
 
** Go to the Implementation properties view and set the ''Implementation Type'' property to ''ProcedureDef''.
 
 
 
The final step is to complete the ''ENSense_Temperatures'' event. The event is a sensing event, sensing is a kind of synchronisation, it synchronises with the ''TCSense_Temperatures'' event. We add formal parameters annotations corresponding to the actual parameters that we have already defined in the task.
 
 
 
*'''Add The Sensed Event Extension'''.
 
** Right-click on the ''ENSense_Temperatures'' Event node.
 
** Select ''New Child/Implementation'' from the menu.
 
** Go to the Implementation properties view and set the ''Implementation Type'' property to ''Sensing''.
 
 
 
We have identified the event as a sensing event. Now we add the parameter direction:
 
 
 
*'''Identify parameter directions'''.
 
** Right-click on the ''t1'' node.
 
** Select''New Child/Parameter Type''.
 
** Go to the ''Parameter Type'' properties view and set the ''Parameter Type'' property to ''formalOut''.
 
** Right-click on the ''t2'' node.
 
** Select''New Child/Parameter Type''.
 
** Go to the ''Parameter Type'' properties view and set the ''Parameter Type'' property to ''formalOut''.
 
 
 
We have now identified the parameters as an formalOut (modelling a simulation's subroutine call return value). This completes the necessary annotations for the simulation, and we can proceed to the translation step. In the event that memory mapped IO is required (non-simulation) then addresses can be added to the model at this stage, before translation takes place. See section on [http://wiki.event-b.org/index.php/Tasking_Event-B_Tutorial#Optional_Annotations_for_Addressed_Variables Addressed Variables] for details.
 
 
 
===== A Summary of Steps =====
 
If generating environment simulation code:
 
# Ensure the Environ Machine is first machine in the development.
 
 
 
For a Tasking Machine definition:
 
# Add the Tasking Machine type (Auto etc).
 
# Add the task type (Periodic etc.).
 
# Define the task priority.
 
# Define the task body.
 
# For each event, add the Event Type.
 
# For each event parameter, add the Parameter Type.
 
# Optionally define addressed variables.
 
 
 
For a Shared Machine definition:
 
# Add the ''SharedMachine'' Machine type.
 
# For each event, define the Event Type.
 
# For each event parameter, define the Parameter Type.
 
 
 
For an Environ Machine definition:
 
# Make the type an Auto Tasking Machine type.
 
# Make the task type Periodic; a shorter period than the shortest task period is best for simulation.
 
# Define the task priority.
 
# Define the task body, it will contain a simulation of changes in the environment.
 
# For each event, add the Event Type.
 
# For each event parameter, add the Parameter Type.
 
# Optionally define addressed variables.
 
 
 
==== Invoking the Translation ====
 
 
 
* To create the IL1 model,
 
** Right-Click on the Main node, select ''Epsilon Translation/Translate Task Mch 2 IL1 EMF''.
 
** Open the Resource Perspective.
 
** Right-click on the ''Heating_ControllerTutorial_Step2'' project folder.
 
** Select refresh, the ''.il1'' file should appear in the project.
 
** Open and inspect the file, and view the source code by opening the IL1 Pretty Print view if desired.
 
 
 
* To create the Event-B model of the implementation,
 
** Return to the Rodin Modelling Perspective.
 
** Right-Click on the Main node, select ''Epsilon Translation/Translate Task Mch 2 Event-B EMF''.
 
** The ''Heating_Controller5AGen'' project is generated, it can be opened and inspected.
 
 
 
There may be errors in the generated machines (the issue will disappear in a future release); these can be fixed in the following way.
 
* Open a Machine in the Event-B Machine Editor.
 
* Select the Edit tab.
 
* Open the REFINES section, the error lies here.
 
* The correct machine is refined, but choose a different machine to refine (any one, it doesn't matter).
 
* Select the original refined machine again.
 
* Save and clean the project, and the error should disappear.
 
* Repeat for the same errors in the other machines; save and clean again.
 
* The machines can viewed as normal using the Rodin editors.
 
 
 
=== Optional Annotations for Addressed Variables ===
 
To use [http://wiki.event-b.org/index.php/Tasking_Event-B_Overview#Implementing_Events memory mapped IO] we can specify which addresses to use. The addresses are added to the event parameters of  a Tasking Machine's sensing and actuating events. The addresses may also be added to the Environ machine's machine variables, for use in simulation. It should be noted that the use of addressed variables, in simulation, has to be done cautiously to prevent memory errors. In the current release the translator generates code for all of these situations, and the environment task should be discarded if simulation is not required.
 
 
 
We now add addressed variable to the ''TCSense_Temperatures'' event in ''Temp_Ctrl_Task1Impl'', a [http://wiki.event-b.org/images/AddressedVarsTask.pdf PrettyPrint] view is available. 
 
 
 
*'''Add Address Information to the ''TCSense_Temperatures'' event'''.
 
** Right-click on the ''t1'' parameter node.
 
** Select''New Child/Addressed Variable''.
 
** Go to the ''Addressed Variable'' properties view and set the ''Address'' property to ''ef14''.
 
** Right-click on the ''t2'' node.
 
** Select''New Child/Addressed Variable''.
 
** Go to the ''Addressed Variable'' properties view and set the ''Address'' property to ''ef18''.
 
 
 
Reads of the monitored variables of the sensing event can therefore be made directly from the address specified. Their is also a ''base'' property which can be set to indicate the base of the property value. The default value is 16. The environment simulation may also make use of addressed variables, but in this case the extension is made to the Environ Machine [http://wiki.event-b.org/images/AddressedVarsEnviron.pdf machine variables].
 
 
 
Invocation of the translators proceeds as detailed above.
 
 
 
 
 
 
[[Category:User documentation]]
 

Revision as of 14:31, 22 December 2020

Back to Theory Plug-in.

Follow this page for the latest on the Theory plug-in. The user manual is also provided together with the installation details.

News

  • 22th December 2020: Version 4.0.1 is released. It requires Rodin 3.5.
  • 19th December 2014: Version 3.0.o is released. It requires Rodin 3.1.
  • 10th July 2014: Version 2.0.2 is released. It requires Rodin 2.8.
  • 24th June 2014: Version 2.0.1 is released. It requires Rodin 2.8.
  • 30th April 2014: Version 2.0.0 is released. It requires Rodin 2.8. This release contains major changes in the features and accessibilities.
  • 20th April 2012: Version 1.3.2 is released. It requires Rodin 2.4.
  • 15th August 2011: Version 1.2 is released. It requires Rodin 2.2.2.
  • 6th August 2011: Version 1.1 is released. It requires Rodin 2.2.2.
  • 8th July 2011: Version 1.0 is released. It requires Rodin 2.2.
  • 22nd May 2011: Version 0.8 released. It is based on Rodin 2.1.1.
  • 11th April 2011: Version 0.7 released. It is based on Rodin 2.1.1.
  • 6th January 2011: Version 0.6 released. It is based on Rodin 2.0.1.
  • 28th October 2010: Version 0.5 released. It is based on Rodin 2.0.

Releases

Version 4.0.1

22th December 2020

Release target: Rodin 3.5

  • Bug fixes:
    • The theory plugin now takes into account updates in theories, as well as creating a theory after using it (there was a cache issue).
    • The error messages at launch about rule-based provers failing to find the context of the proof have been removed.
    • The dropdown list in theory imports is now usable (there was an off-by-one issue when selecting an element in the list).
    • Manually applying an inference rule no longer throws a NullPointerException.
    • It is now possible to rename theories.
    • The TheoryPath creation dialog box has been simplified.
  • Optimizations:
    • The proving interface is now much more responsive, even when a theory contains a lot of rewrite rules (we have implemented a cache of the places where a rewrite rule can apply).
    • The theory plugin now generates much simpler WD conditions, especially for the pred, succ, prj1, prj2, and id operators.
Version 4.0.0-RC1

10th April 2017

Release target: Rodin 3.2

  • AST Extensions (4.0.0) Major API change.
    • Compatibility upgrade to Rodin 3.2
    • Support for get operator position for INFIX extended predicate operators.
    • Improve pattern matching for associative operators.
  • Theory plug-in Branding (0.0.1) Initial version
  • Theory Core (4.0.0) Internal implementation changes.
    • Compatibility upgrade to Rodin 3.2
    • Support for INFIX extended predicate operators.
    • Various bugs fixed.
  • Theory help (2.0.0) User documentations.
  • Theory Keyboard (0.0.1) Initial version (A special plug-in for typesetting Theory).
    • Support for typesetting Real arithmetics (plus, unary minus, multiply, divide, less than, less than or equal, greater than, greater than or equal).
  • Theory Rule-based Prover (4.0.0)
    • Reasoners' input does not contain the proof-obligation context.
    • Use the current sequent's origin to get the proof-obligation context.
    • Bug fixed: translate formula to ensure they have the same formula factory.
    • Added version numbers for reasoners.
    • Automatic rewrite and inference tactics are re-implemented so that each rule application is visible in proof trees.
  • Theory UI (3.0.0)
Version 3.0.0

17th December 2014

Release target : Rodin 3.1

  • migration changes to Rodin 3.1
Version 2.0.2

10th July 2014

Release target : Rodin 2.8

  • bug fixes.
Version 2.0.1

24th June 2014

Release target : Rodin 2.8

  • bug fixes.
Version 2.0.0

30th April 2014

Release target : Rodin 2.8

  • Major changes in the usability.
  • Important bug fixes.
Version 1.3.2

20th April 2012

Release target : Rodin 2.4

  • Important bug fixes.
  • Improvement of deployment and un-deployment wizards
Version 1.2

15th August 2011

Release target : Rodin 2.2.2

  • Bug fixes.
  • Added capability to instantiate multiple theorems at once.
  • Added automatic tactic for expanding operator definitions RbPxd·
Version 1.1

6th August 2011

Release target : Rodin 2.2.2

  • Theory library first version.
  • Bug fixes.
  • Improved UI.
Version 1.0

8th July 2011

Release target : Rodin 2.2

  • Bug fixes.
  • Added import relationships between theories.
  • Added experimental support for recursive definitions.
  • Improved project as well as workspace scope for mathematical and prover extensions.
  • Added tactic (xd) to expand all definitions.
  • Fixed support for polymorphic theorems.
Version 0.8

22nd May 2011

Release target : Rodin 2.1.1

  • Bug fixes.
  • Added import relationships between theories.
  • Added experimental support for recursive definitions.
  • Added project as well as workspace scope for mathematical and prover extensions.
Version 0.7

11th April 2011

Bug fixes. Fixed for Rodin 2.1.1.

Version 0.6

6th January 2011

Minor bug fixes and improvements to theories pretty printer.

Version 0.5

28th October 2010

This is the first release of the Theory plug-in with support for mathematical as well as prover extensions.

Features Requests and Bugs

Please do not hesitate to raise any issues with regards to usability as well as efficiency. Finally, please remember to report any bugs through the SourceForge portal.