number_of_repetitions: Number of Repetitions

In edeaR: Exploratory and Descriptive Event-Based Data Analysis

Number of Repetitions

Description

Provides information statistics on the number of repetitions

A repetition is an execution of an activity within a case while that activity has already been executed before, but one or more other activities are executed in between.

Usage

number_of_repetitions(
  log,
  type = c("all", "repeat", "redo"),
  level = c("log", "case", "activity", "resource", "resource-activity"),
  append = deprecated(),
  append_column = NULL,
  sort = TRUE,
  eventlog = deprecated()
)

## S3 method for class 'eventlog'
number_of_repetitions(
  log,
  type = c("all", "repeat", "redo"),
  level = c("log", "case", "activity", "resource", "resource-activity"),
  append = deprecated(),
  append_column = NULL,
  sort = TRUE,
  eventlog = deprecated()
)

## S3 method for class 'grouped_eventlog'
number_of_repetitions(
  log,
  type = c("all", "repeat", "redo"),
  level = c("log", "case", "activity", "resource", "resource-activity"),
  append = deprecated(),
  append_column = NULL,
  sort = TRUE,
  eventlog = deprecated()
)

## S3 method for class 'activitylog'
number_of_repetitions(
  log,
  type = c("all", "repeat", "redo"),
  level = c("log", "case", "activity", "resource", "resource-activity"),
  append = deprecated(),
  append_column = NULL,
  sort = TRUE,
  eventlog = deprecated()
)

## S3 method for class 'grouped_activitylog'
number_of_repetitions(
  log,
  type = c("all", "repeat", "redo"),
  level = c("log", "case", "activity", "resource", "resource-activity"),
  append = deprecated(),
  append_column = NULL,
  sort = TRUE,
  eventlog = deprecated()
)

Arguments

log	log: Object of class log or derivatives (grouped_log, eventlog, activitylog, etc.).
type	character (default "all"): The type of repetitions: "all" (default), "repeat", or "redo". For more information, see 'Details' below.
level	character (default "log"): Level of granularity for the analysis: "log" (default), "case", "activity", "resource", or "resource-activity". For more information, see vignette("metrics", "edeaR") and 'Details' below.
append	logical (default FALSE) : The arguments append and append_column have been deprecated in favour of augment. Indicating whether to append results to original log. Ignored when level is "log" or "trace".
append_column	The arguments append and append_column have been deprecated in favour of augment. Which of the output columns to append to log, if append = TRUE. Default column depends on chosen level.
sort	logical (default TRUE): Sort output on count. Only for levels with frequency count output.
eventlog	; please use log instead.

Details

Argument level has the following options:

• At "log" level, this metric shows the summary statistics of the number of repetitions within a case, which can provide insights in the amount of waste in a log. Each combination of two or more occurrences of the same activity, executed not immediately following each other, by the same resource is counted as one repeat repetition of this activity.

• On "case" level, this metric provides the absolute and relative number of repetitions in each case.

• On "activity" level, this metric shows which activities occur the most in a repetition. The absolute and relative number of both repeat and redo repetitions is provided by this metric, giving an overview per activity.

• On "resource" level, it can be interesting to have an overview of which resources need more than one time to execute an activity in a case or which resources need to have an activity redone later on in the case by another resource. This metric provides the absolute and relative number of times each resource appears in a repetition.

• On "resource-activity" level, this metric provides specific information about which activities and which resources are involved in the repetitions. For this metric the absolute and relative number of repeat and redo repetitions is provided. Again, two difierent relative numbers are provided, one relative to the total number of executions of the activity in the complete log, and one relative to the total number of executions performed by the resource throughout the complete log.

Similar to the self-loop metric, a distinction should be made between "repeat" and "redo" repetitions, as can be set by the type argument:

• "repeat" repetitions are activity executions of the same activity type that are executed not immediately following each other, but by the same resource.

• "redo" repetitions are activity executions of the same activity type that are executed not immediately following each other and by a different resource than the first activity occurrence of this activity type.

Methods (by class)

• number_of_repetitions(eventlog): Computes the number of repetitions for an eventlog.

• number_of_repetitions(grouped_eventlog): Computes the number of repetitions for a grouped_eventlog.

• number_of_repetitions(activitylog): Computes the number of repetitions for an activitylog.

• number_of_repetitions(grouped_activitylog): Computes the number of repetitions for a grouped_activitylog.

References

Swennen, M. (2018). Using Event Log Knowledge to Support Operational Exellence Techniques (Doctoral dissertation). Hasselt University.

See Also

number_of_selfloops

Other metrics: activity_frequency(), activity_presence(), end_activities(), idle_time(), number_of_selfloops(), number_of_traces(), processing_time(), resource_frequency(), resource_involvement(), resource_specialisation(), start_activities(), throughput_time(), trace_coverage(), trace_length()

edeaR documentation built on April 27, 2023, 9:07 a.m.