How to Analyze a Trace with Ocelotl (obsolete) - soctrace-inria/ocelotl GitHub Wiki

WARNING: this tutorial is obsolete and does not match with the latest Ocelotl version

For the moment, only Pajé trace files are compatible with Ocelotl. An Pajé trace importer is provided in the Ocelotl project (see the related Wiki). A generic module will be available soon for basic analysis of other trace formats. It will be also possible to add its own analysis modules for extern trace formats and other analysis types.

In the tab Time Aggregation

1. Select a trace with the dedicated combo box. If a trace has been imported after Ocelotl is launched, you can actualize trace list with button refresh. Next combos will be available after trace selection.
2. Select a Time Aggregation Operator. This operator will compute a microscopic model of the trace by a time slicing operation. Several operators are available:
   • Pajé format compatible operators:
     1. State Sum: this operator computes a two dimensional matrix where metric is the activity time of each EventProducer by time slice. It is only compatible with PajeSetState events. Once selected, a settings window opens. You need to specify these event types in State Event Types list of this dialog box, and what states are considered as inactive by setting related value in IDLE states list.
     2. State Sum (normalized): same than State Sum, but values are normalized
     3. State Sum Type: same than State Sum, but this time, generated matrix is tri-dimensional and state different values form this new dimension. Specifify inactive states is not mandatory anymore, but stays possible to remove event values that does not interest the analyst. Careful: microscopic model size depends of state value number, and can increase much computation time and memory utilization if they are too numerous. In the case where computation is too long, you should decrease EventProducer or time slice number (tuning of these parameters is explained in following steps)
     4. State Sum Type (PushPop): same than State Sum Type, but compatible with PajePushState and PajePopState events. Should be used if the user does not know trace contents.
3. Select a Space Aggregation Operator. This operator enables to choose different kind of representations of the trace. Their availability depends of which Time Aggregation Operator is selected.
   1. No aggregation: represents the trace with aggregated parts, without displaying information inside each aggregate
   2. State distribution: shows, for each aggregate, the state proportion: this metric is calculated by summing state values of all EventProducers involve in the aggregation, and represented with an area chart. Values that are too weak to be represented are aggregated. Content of each area is shown with a tool tip by hovering the mouse over it.
4. Select EventProducers that will be involved in the analysis. You can Add one or several, Add all or Add Result generated by an other Framesoc tool.
5. Choose time bounds (start and end)
6. Define time slice number: this value will determine how much slices cut the trace. This value influences microscopic model matrix size and should not be too high to avoid a too long computation but also a cluttered visualization (we advise to keep it less than 200).

Some of these parameters are destined to manage big trace analysis and should be set carefully to avoid long computation or memory saturation.

In the tab Advanced Parameters

This part will be completed soon