
Filter Precedence Relations with Identical Resources
Source:R/filter_precedence_resource.R
filter_precedence_resource.RdFilters cases based on the precedence relations between two sets of activities, where both antecendent and consequent have to be executed by the same resource.
Usage
filter_precedence_resource(
log,
antecedents,
consequents,
precedence_type = c("directly_follows", "eventually_follows"),
filter_method = c("all", "one_of", "none"),
reverse = FALSE,
eventlog = deprecated()
)
# S3 method for class 'eventlog'
filter_precedence_resource(
log,
antecedents,
consequents,
precedence_type = c("directly_follows", "eventually_follows"),
filter_method = c("all", "one_of", "none"),
reverse = FALSE,
eventlog = deprecated()
)
# S3 method for class 'activitylog'
filter_precedence_resource(
log,
antecedents,
consequents,
precedence_type = c("directly_follows", "eventually_follows"),
filter_method = c("all", "one_of", "none"),
reverse = FALSE,
eventlog = deprecated()
)
# S3 method for class 'grouped_log'
filter_precedence_resource(
log,
antecedents,
consequents,
precedence_type = c("directly_follows", "eventually_follows"),
filter_method = c("all", "one_of", "none"),
reverse = FALSE,
eventlog = deprecated()
)Arguments
- log
log: Object of classlogor derivatives (grouped_log,eventlog,activitylog, etc.).- antecedents, consequents
charactervector: The set of antecendent and consequent activities. Both arecharactervectors containing at least one activity identifier. All pairs of antecedents and consequents are turned into seperate precedence rules.- precedence_type
character(default"directly_follows"): When"directly_follows", the consequent activity should happen immediately after the antecedent activities.
When"eventually_follows", other events are allowed to happen in between.- filter_method
character(default"all"): When"all", only cases where all the relations are valid are preserved.
When"one_of", all the cases where at least one of the conditions hold, are preserved.
When"none", none of the relations are allowed.- reverse
logical(defaultFALSE): Indicating whether the selection should be reversed.- eventlog
Value
When given an object of type log, it will return a filtered log.
When given an object of type grouped_log, the filter will be applied in a stratified way (i.e. each separately for each group).
The returned log will be grouped on the same variables as the original log.
Methods (by class)
filter_precedence_resource(eventlog): Filters cases for aneventlog.filter_precedence_resource(activitylog): Filters cases for anactivitylog.filter_precedence_resource(grouped_log): Filters cases for agrouped_log.
References
Swennen, M. (2018). Using Event Log Knowledge to Support Operational Exellence Techniques (Doctoral dissertation). Hasselt University.
See also
Other filters:
filter_activity(),
filter_activity_frequency(),
filter_activity_instance(),
filter_activity_presence(),
filter_case(),
filter_case_condition(),
filter_endpoints(),
filter_endpoints_condition(),
filter_flow_time(),
filter_idle_time(),
filter_infrequent_flows(),
filter_lifecycle(),
filter_lifecycle_presence(),
filter_precedence(),
filter_precedence_condition(),
filter_processing_time(),
filter_resource(),
filter_resource_frequency(),
filter_throughput_time(),
filter_time_period(),
filter_trace(),
filter_trace_frequency(),
filter_trace_length(),
filter_trim(),
filter_trim_lifecycle()