pm4py.objects.dcr.utils package#
Submodules#
pm4py.objects.dcr.utils.utils module#
- pm4py.objects.dcr.utils.utils.time_to_iso_string(time, time_precision='D')[source]#
Parameters#
time time_precision: valid values are D H M S
Returns#
- pm4py.objects.dcr.utils.utils.clean_input(graph: DcrGraph, white_space_replacement=None, all=False)[source]#
- pm4py.objects.dcr.utils.utils.map_labels_to_events(graph)[source]#
Events, ids are unique (and are often derived from the concept:name attribute) Labels or activities are not unique (in general do not have an equivalent in event log nomenclature). Many events or ids can map to an activity or label. At most one label/activity for an event/id. In Dcr Discovery algorithms usually 1 event/id = 1 label/activity. So we can simplify the mapping.
- pm4py.objects.dcr.utils.utils.time_to_int(graph: TimedDcrGraph, precision='days', inplace=False)[source]#
- pm4py.objects.dcr.utils.utils.get_reverse_nesting(graph: HierarchicalDcrGraph)[source]#
- pm4py.objects.dcr.utils.utils.nested_groups_and_sps_to_flat_dcr(graph: HierarchicalDcrGraph) DcrGraph[source]#