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.
[ProM-developers] Classifiers
This morning Eric send the following message to the ProM Developers mailing list:
Dear all,
This weekend, we noticed that some plug-ins ‘massage’ the result of classifier to obtain the result from a different classifier. For example, if the result of the concept name classifier would be “X”, then “X+complete” would be a valid result from the standard classifier. *Please do not do this*. If you need to know the results of some classifier on some event, run the classifier on the event, and do not start guessing around with the results of other classifiers. For example, if the result of the standard classifier is “X”, then *do not assume* that “X”is of the form “Y+Z” and do not start looking for the Y –part to obtain the result of the name classifier. First of all, we just might change the “+” into some other string, second, we just might swap “Y+Z” to “Z+Y”, and third, Y itself may contain several instances of “+” which would result in strange results.
Please note that it is not hard to obtain the results from a classifier, as the class XLogInfoImpl has a number of classifiers predefined:
- XLogInfoImpl.STANDARD_CLASSIFIER(event)
- XLogInfoImpl.NAME_CLASSIFIER(event)
- XLogInfoImpl.RESOURCE_CLASSIFIER(event)
- XLogInfoImpl.LIFE_CYCLE_CLASSIFIER(event)
If you know that your plug-in relies on assumptions as mentioned above, please change your plug-in accordingly.
Finally, please note that at 12:30 we have another ProM lunch today. Dirk Fahland will introduce us to the way he has his plug-ins tested by the Hudson server.
Cheers,
Eric.
Dear all,
This weekend, we noticed that some plug-ins ‘massage’ the result of classifier to obtain the result from a different classifier. For example, if the result of the concept name classifier would be “X”, then “X+complete” would be a valid result from the standard classifier. *Please do not do this*. If you need to know the results of some classifier on some event, run the classifier on the event, and do not start guessing around with the results of other classifiers. For example, if the result of the standard classifier is “X”, then *do not assume* that “X”is of the form “Y+Z” and do not start looking for the Y –part to obtain the result of the name classifier. First of all, we just might change the “+” into some other string, second, we just might swap “Y+Z” to “Z+Y”, and third, Y itself may contain several instances of “+” which would result in strange results.
Please note that it is not hard to obtain the results from a classifier, as the class XLogInfoImpl has a number of classifiers predefined:
- XLogInfoImpl.STANDARD_CLASSIFIER(event)
- XLogInfoImpl.NAME_CLASSIFIER(event)
- XLogInfoImpl.RESOURCE_CLASSIFIER(event)
- XLogInfoImpl.LIFE_CYCLE_CLASSIFIER(event)
If you know that your plug-in relies on assumptions as mentioned above, please change your plug-in accordingly.
Finally, please note that at 12:30 we have another ProM lunch today. Dirk Fahland will introduce us to the way he has his plug-ins tested by the Hudson server.
Cheers,
Eric.
Joos Buijs
Senior Data Scientist and process mining expert at APG (Dutch pension fund executor).
Previously Assistant Professor in Process Mining at Eindhoven University of Technology
Senior Data Scientist and process mining expert at APG (Dutch pension fund executor).
Previously Assistant Professor in Process Mining at Eindhoven University of Technology
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
- 393 - Usage
- 287 - Development
- 9 RapidProM
- 1 - Usage
- 7 - Development
- 54 ProM5
- 19 - Usage
- 187 Event Logs
- 32 - ProMimport
- 75 - XESame