Skip to content
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

fuzzymineR::mine_fuzzy_model() triggers error from xesreadR::write_xes() #1

Open
billster45 opened this issue Dec 7, 2019 · 2 comments

Comments

@billster45
Copy link

Hi,

Thank you for creating this package. Really looking forward to using it.

Was just testing it with sample data using the hospital billing log from evendataR as follows..

metrics <- fuzzymineR::mine_fuzzy_model(eventdataR::hospital_billing)

..it triggers this error....

Error in apply(trace_events, 1, addEvent) : dim(X) must have a positive length

By running the function fuzzymineR::mine_fuzzy_model() line-by-line I can see the error is when the function uses xesreadR::write_xes() here..

https://github.com/nirmalpatel/fuzzymineR/blob/master/R/mine_fuzzy_model.R#L102

And I think the error ultimately comes from this part of xesreadR::write_xes()
https://github.com/bupaverse/xesreadR/blob/master/R/XES.r#L110

Trying the function with some of the other sample logs the same error is not triggered. For example,...

metrics <- fuzzymineR::mine_fuzzy_model(eventdataR::traffic_fines)

Do you think this is an issue with xesreadR::write_xes() that should be fixed? For example like this https://stackoverflow.com/a/28423503

Or perhaps some of the sample logs like hospital billing need some kind of pre-processing before they will work in fuzzymineR::mine_fuzzy_model()

Thanks

@nirmalpatel
Copy link
Collaborator

Hey @billster45 thanks for reporting the issue! Just noticed this! We haven't been actively maintaining the repository, but we have one more issue being reported, so I think it's time to maintain the package.

Right off the bat, we have had issues when event names contain special characters, so I have used regex to preprocess data in a few instances. I'll look into the issue and see what I can find out.

@nirmalpatel
Copy link
Collaborator

Hey @billster45 we updated the package a couple of weeks ago and switched to ProM 6.10. can you give it one more try and see what happens?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants