Merge Two Event Logs With AIS Algorithm

Merge event logs

The Merge Two Event Logs With AIS Algorithm plugin can be used to automatically merge two logs into one log. If you want to use this algorithm, you can just work with the default settings or for more experienced users we recommend inspection of these settings. You can optimise the algorithm by adapting the settings (based on your knowledge of the logs you are trying to merge). Here is a short overview of the meaning of the settings:
Score settings

  • Same case id: with this indicator score you determine how certain you are that if traces in both logs have equal case identifiers, they belong to the same process instance.
  • Same originator: with this indicator score you determine how certain you are that if trace in both logs have equal originators, they are more probable to belong to the same process instance.
  • Same attribute value: with this indicator score you determine how certain you are that if events in the traces of both logs have equal attribute values (like e.g. a customer numer, order number, ...), they belong to the same process instance. Note that event names do not need to correspond.
  • Extra trace: with this indicator score you determine how certain you are that a trace from one of the logs has only one trace in the other log that belongs to the same process instance. Increase the negative value of this punishment score value if too many traces were merged together in one trace in the merged log.
  • Missing trace: with this indicator score you determine how certain you are that a trace from one of the logs has at least one trace in the other log that belongs to the same process instance. Increase the negative value of this punishment score value if too few traces were merged together in one trace in the merged log.
  • Time difference: with this indicator score you determine how certain you are that traces in both logs belong to the same process instance if they happened closely together in time.
  • Maintain order: select this check box if only traces in the second log can belong to the same process instance as a particular trace in the first log if they start after the particular trace of the first log started.
Algorithm settings (see paper)
  • Max num generations: the maximal number of inspected generations of solutions.
  • Max num no optimalisations: the maximal number of inspected generations with no optimalisations (the amount of consecutive generations with no improvements that will make the algorithm stop earlier).
  • Num initial solutions for generations: the number of solutions considered for each generation.
  • Num solutions in generation: the number of solutions in each generation.
  • Perc best solutions for clonal selection: the percentage of best solutions of a generation to be selected in the clonal selection phase.
  • Perc best solutions for receptor editing: the percentage of best solutions of a generation to be selected in the receptor editing phase.
This plugin is released as a part of the LogMerge package which is included in ProM 6.1 or which can be downloaded here.
Merge event logs - screenshot 1 Merge event logs - screenshot2 Merge event logs - screenshot3 Merge event logs - screenshot4

This plugin was used in