You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am analyzing an event log in which for a number of traces, several activities are initiated at the same time; there is no delay between these events. I have an issue when trying to display this event log in a process map. More specifically, the time between events that are initiated at the same time is displayed as negative. I deduced that this is the negative of the processing time of the previous event.
Am I perhaps doing something wrong with the activity instance?
eventdata_combined <- eventdata_combined[, activity_instance := 1:.N]
#From wide to long
eventdata_combined <- as.data.table(gather(eventdata_combined, time_type, timestamp,
c("start_time", "completed_time"), factor_key=TRUE))
So the rows for start_time and completed_time for one event have the same activity instance number.
The text was updated successfully, but these errors were encountered:
This behaviour is as expected actually. The point is that process maps are not suitable for visualizing event logs with a lot of concurrent events. If A, B and C start at the same time, the process map will always show them as a sequence, depending which comes first in the data. Let's say A > B > C. The flow time from A to B will be start(B) - end(A), and since end(A) = start(A) + duration(A), flow(A,B) = start(B) - start(A) - duration(A). And since start(A) = start(B), flow(A,B) = -duration(A).
Other process mapping tools, such as disco, detect if two activities are concurrent, and will show them not as a sequence, but as follows:
In bupaR, we decided no to go for this, but this can get ambigous. Unless you keep a close look on the number, it seems there is a choice between A, B and C. In bigger maps, choices and concurrency can get mixed up. Process maps in bupaR consistently show arrows between the last and next activity, regardless whether they overlap or not.
As an alternative, you might want to look at more advanced discovery algorithms using pm4py or heuristicsminer
(For the former, you need to have a Python installation)
If you have any suggestion how to better cope with this issue in a process map, please let us know! For example, what would you expect the process map to be like?
I am analyzing an event log in which for a number of traces, several activities are initiated at the same time; there is no delay between these events. I have an issue when trying to display this event log in a process map. More specifically, the time between events that are initiated at the same time is displayed as negative. I deduced that this is the negative of the processing time of the previous event.
Am I perhaps doing something wrong with the activity instance?
So the rows for start_time and completed_time for one event have the same activity instance number.
The text was updated successfully, but these errors were encountered: