Derive Events using rules
Given an log path and, set of rules, they are channelised to event derivation algorithm. Event derivation algorithm is responsible for building the transformed log. Evaluation metrics and log statistics for both, original log and transformed log are caomputed and returned.
Call apply_trans(logpath, activities, attributes, predicates, thresholds, location, new_activities, window, order_flag, visual_flag) It takes as input
1. logpath (str): Path of event log
2. activities (List of str): List of activities in rule
3. attributes (List of str): List of attributes in rule
4. predicates (List of str): List of predicates in rule
5. thresholds (List of float or str): List of thresholds in rule
6. location (List of str): List of locations for derived events in rule
7. new_activities (List of str): List of derived event's identifiers
8. window (List of int): List of time windows in rule
9. order_flag (bool): Flag to denote if order of events in log is considered
10.visual_flag (bool): Flag to denote if activities in rule should be retained
The resulting transformed event log can be found in the same location as that of original log with same name suffixed with "modified" keyword.
Installation
pip install derive_event_pm4py
How to use it?
Install derive_event_pm4py package. Following, from derive_event import apply_trans.
Example:
path = "<path>\<file>.xes"
act = [["E", "F"], ["E", "G"], ["E", "H"]]
attr = [["additional", "additional"], ["additional", "additional"], ["additional", "additional"]]
pred = [["LT", "LT"], ["LT", "GT"], ["LT", "GT"]]
thres = [[100, 50], [100, 40], [100, 50]]
loc = ["end", "end", "end"]
new_act = ["EF", "EG", "EH"]
window = [432000, 432000, 432000]
order = [False, False, False]
visual = False
apply_trans(path, act, attr, pred, thres, loc, new_act, window, order, visual)
License
Copyright (c) 2020 Ajay Pandi
This repository is licensed under the MIT license. See LICENSE for details.
Metadata
Release files for derive-event-pm4py 1.0.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| derive_event_pm4py-1.0.1.tar.gz | 7.0 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| derive_event_pm4py-1.0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 14.8 kB
Release files / derive_event_pm4py-1.0.1.tar.gz
| Download URL | derive_event_pm4py-1.0.1.tar.gz |
|---|---|
| Size | 7.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d59324e6e273631f5d334102e703d9ebd4710aa1af309ec256afeb4a50c0dee4
|
|
BLAKE2b-256 checksum How to use checksums |
4b75a3699d1431fec54fe215ee51e634bf095d59e0822d9969b8eb3d90423b48
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.2.0 pkginfo/1.6.1 requests/2.22.0 setuptools/54.1.1 requests-toolbelt/0.9.1 tqdm/4.54.1 CPython/3.7.4
|
Release files / derive_event_pm4py-1.0.1-py3-none-any.whl
| Download URL | derive_event_pm4py-1.0.1-py3-none-any.whl |
|---|---|
| Size | 7.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
5246e18e59672ba374114b03a8ae1fb8e85f0dc843a9662f3b5d50a4aaa70af6
|
|
BLAKE2b-256 checksum How to use checksums |
19c2dafe4833f11b96f96369b533210c8070275a7bfd03903d9352724180be11
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.2.0 pkginfo/1.6.1 requests/2.22.0 setuptools/54.1.1 requests-toolbelt/0.9.1 tqdm/4.54.1 CPython/3.7.4
|
Security for derive-event-pm4py 1.0.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.