Random fitness/precision result from token replay

[fmannhardt]

We have got a bug report over at the R pm4py binding that the token replay (which we have as a default -- which should be changed I guess) gives back random results for the same model and event log when called multiple times. You can find the original bug report here:
bupaverse/pm4py#6

Is this expected behaviour? If not I can try to make the test model and log available.

[fit-alessandro-berti]

Dear Felix,

We are aware of some problems if the model contains duplicate transitions (the method cannot handle duplicate transitions properly; hence in the last release we introduced a new version of the token-based replay based on a backwards state space exploration)

However, if the model does not contain duplicate transitions, then it's weird. If you can please provide us the test model and log

Sincerely
Alessandro

[fmannhardt]

This is the model:

But, I just checked it directly with PM4Py and the token replay gives consistent results. It does not find that the model perfectly fits all traces (alignment-based fitness is 1.0) but it gives always the same fitness of 0.96905...

I will investigate what goes wrong in the automatic conversion from R.