Simulation can record all States,Transitions and Truth-Table lines that were visited during a simulation run, as well as executed mini-specs and static-reactions.
To create an execution log file:
1. Select Options > Test Settings from the Simulation Profile Editor menu. The Test Settings dialog box opens.
2. Check the Create Execution Log box.
3. Press OK, the log file will be created during Simulation execution.The execution log file is named execution-<date-time>.trace and created under the ana/<profile name> directory in the workarea.
The logging continues into the same file until 'Quit' or 'Rebuild' operation. 'Rebuild' operation start a new execution log file.
The format of the execution log file is a list of:
The separator '^' is used for Activity/States of generic instances.
Mini-spec and Static-reaction executed actions are logged in the following format:
<State/Activity Id> Action{<action part of the triggered expression>}Action ExecutedAction{<actually executed action>}ExecutedAction
A single Action{<expression>}Action may be followed by none, one or many ExecutedAction{<action>}ExecutedAction
25663300660245681^2533300560199684
2566300660245681^2533300560199685
2566300660245681^2533300560199686
2566300660245681^2533300560199687
2533343509872644 Action{for $I in MIN_IND to (MAX_IND-1) loop MY_INT_ARR_GOOD($I)=STRING_LENGTH(CONST_STR_ARR($I)); end loop;MY_INT_ARR_GOOD(MAX_IND)=1000-1}Action ExecutedAction{for $I in MIN_IND to (MAX_IND-1) loop MY_INT_ARR_GOOD($I)=STRING_LENGTH(CONST_STR_ARR($I)); end loop}ExecutedAction ExecutedAction{MY_INT_ARR_GOOD(MAX_IND)=1000-1}ExecutedAction
2533300560199681^3940679738720256 1
2533300560199681^2251825583488024 6
2533283380330502 Action{SUB_BY_TT1(IN_SUB_TT1,IN_SUB_TT2,OUT_SUB_TT1,OUT_SUB_TT2)}Action
2533347804839940 Action{SUB_BY_STM_ACT_LANG(B1,BA1,C1,E1,I1,R1,S1)}Action ExecutedAction{SUB_BY_STM_ACT_LANG(B1,BA1,C1,E1,I1,R1,S1)}ExecutedAction