vsTASKER 7 User Manual
×
Menu
Index

On Time

 
On Time
1

Name

1. Name
Name of the Transition inside the logic.
This name can be used to retrieve the object (instance) in case user wants to activate it from source code.
 
2

Group

2. Group
If a Transition is part of a Group, it will be named here.
A Group can also be part of another Group, thus, a Group name will be the concatenation of all nested Group names: group1::group2::..::group3 (here, group3 being the deepest one).
 
3

Activation

3. Activation
Select on which condition the Transition must activate or deactivate the object it is linked to:
 
  • On Time: See below
  • On Reaction: See here
  • On Condition: See here
 
4

Persistent

4.
By default, when a Transition is triggered, it will not be reactivated even if the same condition occurs.
If Persistent mode is selected, the Transition reactivates itself automatically after start and is ready at next cycle.
This might lead to unwanted behavior.
 
5

Fixed Time

5. Fixed Time
When Fixed Time is selected, as soon as the specified time is elapsed, the Transition triggers.
For i.e: if the Transition is connecting Task A with Task B with a Fixed Time set to10 seconds. If the Logic is triggered 1 minute after the simulation start, then the Transition will be triggered 1 minute 10 seconds after the simulation start and Task A will be left for Task B.
 
6

Absolute Time

6. Absolute Time
If this option is checked (for Fixed or Random Time), the specified Time is according to the simulation time.
Transition triggers when the simulation time is greater than the given fixed or random time
 
7

Random Time

7. Random Time
A random value (according to the Distribution) will be taken at Transition initialization. This random value between Min and Max values will act as Fixed Time.
 
 
8

Distribution

8. Distribution
Linear: Random values are distributed equally between Min and Max
Gaussian: Random values are distribution according to a Gaussian curve between Min and Max. Mid-term has the highest probability of occurrence.
 
9

When Done

9. When Done
Specify here the Event or Fact that will be triggered after activation of the Transition (optional).
 
10

On Trigger

10. On Trigger
 
Write here the code you like to be run once after the activation of the Transition.
The user can put whatever C/C++ code he wants there. This code can access all vsTASKER API, all included third-party APIs and all user designed scenario, entity, logic, knowledge and model data of the current database.
11

Help

11. Help
Put here whatever description of information useful to the designer to understand what the Transition is about.
The help part is also used in the hint and the automatic document generation (see Make Documents).