Demo Log Manipulation - pm4knime/pm4knime-document GitHub Wiki

In this part, the demand to manipulate an event log is shown at first. Next, the concrete workflow is provided as one sample to solve a similar problem. https://github.com/pm4knime/pm4knime-document/blob/master/images/demo-simple-log-manipulation.PNG

One example workflow with PM4KNIME is shown below:

https://github.com/pm4knime/pm4knime-document/blob/master/images/demo-simple-log-manipulation-wf.PNG

The steps to create the workflow above are

  1. Download the dataset from github. Extract the event log file running-example.xes from the downloaded dataset.
  2. Import running-example-non-conforming.xes and running-example-just-two-cases.xes into KNIME with two nodes Event Log Reader.
  3. Filter the event log running-example-non-conforming.xes with node Filter Event Log. Here, to filter the traces with Resource "Pete", meanwhile, the traces without the Resource "Pete" are ignored, the configuration is set in the next figure.
    image

After execution, it splits the log into two logs, one is the log to keep, the other is to dispose. image

image

  1. Merge two event logs with node Merge Log

  • Connect the output ports from the filtered event logs and the imported event log.

  • Configure with Merge Strategy Separate Trace, it simply combines the traces from the two event logs together. Traces with the same caseID are allowed in the merged event log.

  • Configure with Merge Strategy IgnoreTrace, it ignored the traces from the second event log with the same caseID from the first event log.

  • Configure with Merge Strategy Internal Trace Merge, for the traces with the same caseID, it combines the events from the two traces together. The trace attributes can be chosen for the new attributes. The next figure shows the configuration example. image

  • Configure with Merge Strategy Internal Event Merge, for the events with the same names in the traces with the same caseID, it creates one new event and with the chosen attributs.

  • Choose strategy Internal Trace Merge and execute the node. It results in the merged event log. image

  1. Classify the traces in the event log with certain attributes.
  • Configure
  • Execute the nodes. It outputs the result as following.

Notice

The event log manipulation can be achieved by applying the KNIME manipulation on Data Table which is converted from the event log. However, those operations can be simplified with the node provided before.