pm4py / pm4py-core

Public repository for the PM4Py (Process Mining for Python) project.
https://pm4py.fit.fraunhofer.de
GNU General Public License v3.0
722 stars 286 forks source link

Why do many functions that calculate duration only use timestamp_key instead of reserving start_timestamp and timestamp_key at the same time. #411

Closed DAAworld closed 1 year ago

DAAworld commented 1 year ago

I wonder if pm4py didn't consider the start and end time in the log at the same time, because many functions that calculate the duration only use timestamp_key instead of reserving start_timestamp and timestamp_key at the same time.

fit-alessandro-berti commented 1 year ago

Dear @DAAworld

Most process mining algorithms consider naturally events with just a timestamp. Very few use the start/end timestamp information.

In pm4py, some methods offer support for start/end timestamps, however, the support is not systematic and limited to few algorithms.

DAAworld commented 1 year ago

Dear @DAAworld

Most process mining algorithms consider naturally events with just a timestamp. Very few use the start/end timestamp information.

In pm4py, some methods offer support for start/end timestamps, however, the support is not systematic and limited to few algorithms.

Yes, I noticed, so, in some needed methods, I can only modify it myself. Have you considered making some changes in the future?

fit-alessandro-berti commented 1 year ago

As long term plan yes, but that also depends on the development of process mining algorithms that use the lifecycle information in a more effective way