-
Notifications
You must be signed in to change notification settings - Fork 300
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
log_to_feature returns unexpected features when extracting follows relations #293
Comments
Dear Felix, We will propose a fix for this in one of the upcoming releases. The problem currently is that if no attribute is provided for neither the string/numeric event/trace attributes, then a default selection is applied for these attributes. |
This issue is fixed in https://github.com/pm4py/pm4py-core/releases/tag/2.2.17 |
I am trying the same call again in PM4Py 2.2.30 and I am afraid it is still not fully fixed. I am getting the following response:
For a call with:
Same file as used above. |
Dear Felix, This behavior is triggered when you provide None to all the four different type of features (str_ev_attr, str_tr_attr, num_ev_attr, num_tr_attr). In that case, the algorithm assumes no feature is manually provided and proceed to automatic detection. Try to provide empty lists instead of None for all the voices and only the successions should be returned then. |
I provided None only to the first four arguments, the last argument |
I was refactoring my code to use the new method
log_to_feature
instead of the old deprecated variant of it.Now the following code returns more than just the 2grams or directly follow relations:
The list of features is:
Expected result would be:
I am using PM4Py v2.2.16
Here is the file I am using:
sepsis.csv
.
The text was updated successfully, but these errors were encountered: