Tutorial Animation Tips: Difference between revisions

Line 172: Line 172:

This instance machine acts a bit like a configuration file for ProB.
This instance machine acts a bit like a configuration file for ProB.
In Event-B you can use the extends concept for contexts to achieve this effect,
[[Tutorial_Rodin_Parameters#Using_contexts_for_ProB_animation|as explained here]].

Latest revision as of 08:37, 3 May 2023

Make sure you have the Lift.mch model from the first part of the tutorial: Starting ProB and first animation steps.

Operation with many solutions for the parameters

Add the following operation to the Lift model:

jump(level) = PRE level : 0..99 THEN floor := level END

Now reload your model and initialise the machine. Your ProB window should now look as follows:

ProB LiftWithJump.png

As you can see, only 10 values for the level parameter of the jump operation are displayed in the "Enabled Operations" pane. The orange "max" button to the left of "Enabled Operation" tells you that not all possible parameter values for the operations were computed.

There are several solutions to overcome this.


First, you could increase the "MAX_OPERATIONS" preference of ProB by selecting the "Animation Preferences" command in the "Preferences" menu:


You should then set the preference "" to at least 101 and then re-load the B machine.

ProB Lift OpPane WithJump101.png

Note there is another preference "MAX_INITIALISATIONS" which controls how many solutions are computed for SETUP_CONSTANTS and for INITIALISATION.

Note: you can also set either of these preferences to 0. In this case, no solutions will be automatically be pre-computed for you, but you can use "Execute an Operation..." below. You can then also double-click on individual operation names for this.

Increasing MAX_OPERATIONS for an individual operation

As of version 1.9.0 of ProB you can also set the MAX_OPERATIONS limit individually per operation. For this you need to add a declaration in the DEFINITIONS section of your B machine:

   MAX_OPERATIONS_jump == 101

Executing an Operation by Predicate

The alternative is to provide the parameter value for level yourself. For this, select the "Execute an Operation..." command in the animate menu:

ProB Lift ExecuteOperationMenu.png

After that, select the jump operation

ProB ExecuteOperation.png

and you will be provided with the following dialog:

ProB Lift ExecuteOperation Dialog.png

Type in 98 into the level field and hit the "Execute" button.

ProB Lift OpPane WithJump Exec98.png

Note: instead or in addition to providing concrete values, you can also specify a predicate that constrains the values of the parameters:

ProB Lift ExecuteOperation Dialog Pred.png

The above predicate, level>96 & level mod 2 =0 would select the same value 98 for level. When there are multiple solutions, ProB will only execute the operation for the first solution found.

Using Random enumeration

You can also tell ProB to try and perform random enumerations. This feature is available in ProB 1.5.0 or newer. You add the following lines to your model:


Alternatively, you can set this preference using the "Advanced Preferences" pane in the Preferences menu. After reloading the machine you should see a picture similar to the following one:

ProB Lift Randomise.png

Using Constraint-Based Validation Techniques

Find Sequence

You can also use the constraint solver to construct sequences which are of interest to you. Let us add the following operation to the lift model:

top_reached = PRE floor=99 THEN skip END

Now suppose we want to execute this new operation as early as possible. We can ask the constraint solver to generate a feasible sequence of operations. First select the "Find Sequence..." command in the Verify menu:


Now type in

 jump ; top_reached

in this dialog box:


ProB will then find a solution operation sequence for you and execute it:


Constraint-Based Model-Based Testing

Alternatively, you could for example use the constraint-based test-case generator to find for every operation the shortest trace that enables it.

First select the "Constraint-based Testcase Generation.." command in the Analyse menu:


Now click on the ok button in the dialog box (which allows you to select the target operations to cover in the generated test cases):


ProB will then find four test cases for you, one for each operation:


You can also visualise these test cases as a tree by clicking the "View Tree" button:


Green entries show test cases (traces which cover an operation in the shortest possible way), gray entries are traces which did not contribute to a test case.

More details are available in the Tutorial_Model-Based_Testing and Tutorial_Model_Checking,_Proof_and_CBC sections.

Using Trace Replay

You can store traces in JSON format using ProB. These traces contain values for the constants, initial values and operation arguments. If you wish you can generate such traces programmatically or modify them by hand and try to replay them.


If you have many possible valuations for constants you may want to consider to generate one or more instantiations of your machine for animation or model checking.

For example, given a machine


In classical B you can use EXTENDS to create an instantiation machine:

MACHINE Instance1
CONSTANTS peter, paul, mary
  USERS = {peter,paul,mary} &
  card({peter,paul,mary}) = 3 & // all different
  root = mary

This instance machine acts a bit like a configuration file for ProB. In Event-B you can use the extends concept for contexts to achieve this effect, as explained here.