To prevent spam users, you can only post on this forum after registration, which is by invitation. If you want to post on the forum, please send me a mail (h DOT m DOT w DOT verbeek AT tue DOT nl) and I'll send you an invitation in return for an account.
Using Replay a log on Petri Net for Conformance Analysis plugin
Hi everyone,
I have tried to use "Replay a log on Petri Net for Conformance Analysis" plugin to check the alignment between some logs and models. Each name of events in the log exactly matches the name of the corresponds transition in the Petri net. The replay result when - I visualized it by using Project Alignment to Log (PNetReplayer) - shows that Cases replayed, in STATS FORM RELIABLE ALIGNMENTS, are 0. Also, all alignments are not reliable. Any ideas why is this happen?
Cheers,
H.
I have tried to use "Replay a log on Petri Net for Conformance Analysis" plugin to check the alignment between some logs and models. Each name of events in the log exactly matches the name of the corresponds transition in the Petri net. The replay result when - I visualized it by using Project Alignment to Log (PNetReplayer) - shows that Cases replayed, in STATS FORM RELIABLE ALIGNMENTS, are 0. Also, all alignments are not reliable. Any ideas why is this happen?
Cheers,
H.
Comments
-
Hi,The most likely explanation for this is that your model does not allow you to reach the final marking from the initial marking.One of the requirements on an alignment is that it forms an executable path in the model from the initial marking to the final marking. If no such path exists, the alignment is called unreliable.Kind regards,Eric.
-
Hi Eric,Thank you for your response.You’re definitely correct. The models were not sound and there were deadlocks.
Kind regardsH.
Howdy, Stranger!
Categories
- 1.6K All Categories
- 45 Announcements / News
- 225 Process Mining
- 6 - BPI Challenge 2020
- 9 - BPI Challenge 2019
- 24 - BPI Challenge 2018
- 27 - BPI Challenge 2017
- 8 - BPI Challenge 2016
- 68 Research
- 1K ProM 6
- 394 - Usage
- 288 - Development
- 9 RapidProM
- 1 - Usage
- 7 - Development
- 54 ProM5
- 19 - Usage
- 187 Event Logs
- 32 - ProMimport
- 75 - XESame