This FAQ is a living document. If you haven’t found the answer to
your question here or anywhere else on our website, contact us via support@bupar.net, and we will get
back to you as soon as we can. If you want to notify us of a bug in one
of the bupaR
-packages, please submit an issue on the
respective GitHub-repository.
activitylog
object class, as specified in Scenario 1.assign_instance_id()
.eventlog()
will perform some checks to make sure the provided mapping corresponds to the data model. This means that each value of the activity_instance_id
should be connected to a single case_id
and a single activity_id
. For larger event logs, this does take some time. You can circumvent these by setting the argument validate = FALSE
.eventlog
or activitylog
object. The activitylog
is a simplified object class that does not require special validation. bupaR
does not contain a magic slider that can simplify a process_map
. We believe that process maps should always be a transparent visualization of the log, and simplifying should be done by the conscious use of filters. You might consider filter_infrequent_flows()
, filter_trace_frequency()
or filter_activity_frequency()
for this job.renderProcessMap()
in the Server, and processMapOutput
in the UI of your app. Make sure to use the width
and height
arguments to set proper dimensions for the map.export_map()
. To do this, note that you should use the argument render = FALSE
in the call to process_map()
. Use the argument title
to add a caption to the image, and width
and height
to adjust the file dimensions.Copyright © 2023 bupaR - Hasselt University