Treffer: OC-DECLARE: Discovering Object-Centric Declarative Patterns with Synchronization (aarkue/oc-DECLARE: v0: OC-DECLARE Initial Version)

Title:
OC-DECLARE: Discovering Object-Centric Declarative Patterns with Synchronization (aarkue/oc-DECLARE: v0: OC-DECLARE Initial Version)
Authors:
Publisher Information:
Zenodo
Publication Year:
2025
Collection:
Zenodo
Document Type:
E-Ressource software
Language:
unknown
DOI:
10.5281/zenodo.15554279
Rights:
Creative Commons Attribution 4.0 International ; cc-by-4.0 ; https://creativecommons.org/licenses/by/4.0/legalcode
Accession Number:
edsbas.25B2D36A
Database:
BASE

Weitere Informationen

OC-DECLARE See https://github.com/aarkue/oc-DECLARE for the most up-to-date version of this codebase. This repository contains the following parts: 1. Visual Editor for OC-DECLARE2. Backend for Conformance Checking and Discovery of OC-DECLARE3. Evaluation Setup used to evaluate OC-DECLARE4. Evaluation Dataset and Results for OC-DECLARE There is an interactive web demo of OC-DECLARE available at https://oc-declare.vercel.app/.It can be used directly in your browser and without installing anything. Note, that the web version is slower and less scalable than running the approach natively. However, it is great for experimenting or quickly trying out the OC-DECLARE implementation. In the web version, OCEL 2.0 files in the XML and JSON format are supported. Discovery in the web version does not use object-to-object (O2O) relationships.See https://www.ocel-standard.org/event-logs/overview/ for a list of publicly available example datasets. Details The backend of the OC-DECLARE approach is implemented in the Rust programming language.See https://www.rust-lang.org/tools/install for instructions on how to install Rust on your machine. Backend & Evaluation Setup Conformance Checking and Discovery for OC-DECLARE is implemented in the `shared` crate (`crates/shared`).The functions `get_for_all_evs_perf` (for conformance checking) and `discover` (for discovery) are probably the most interesting ones.The shared backend code can be compiled by running `cargo build --release` in the `shared` directory. The evaluation setup is available in the `evaluation` crate (at `crates/evaluation`).It can be executed with `cargo run --release -- /path/to/ocel/folder/`, where the appropriate OCEL 2.0 JSON files are expected to be available (e.g., `ContainerLogistics.json`).The evaluation pipeline will then run through all configurations and place the result files in the current directory (e.g., `crates/evaluation`).For each configuration (OCEL file and O2O direction), two files are created ending in `-results.json` for JSON representation ...