PDC 2022 is the 2022 edition of the Process Discovery Contest.

#### There can be only one…

##### Do you believe you have implemented a good discovery algorithm?

Then submit it to the PDC 2022 to put it to the test!

The PDC 2022 test contains 480 event logs, for which a model needs to be discovered (*training* logs), and 96 pairs of event logs that are used to evaluate the discovered models (*test* logs and *base* logs) .

The 96 pairs of test logs and base logs are all generated using the same configurable model, which was inspired by a model from a real-life event log and has the following configurable options:

- Long-term dependencies: yes/no
- Loops: no/simple/complex
- A simple loop has a single point of entry and a single point of exit.
- A complex loop has multiple points of entry and/or multiple points of exit.

- OR constructs: yes/no
- Routing constructs: yes/no
- Optional tasks: yes/no
- Duplicate tasks: yes/no

Each pair is matched by five training logs:

- A training log without noise.
- A training log where in every trace with probability 20% one random event is removed.
- A training log where in every trace with probability 20% one random event is moved to a random position.
- A training log where in every trace with probability 20% one random event is copied to a random position.
- A training log where in every trace with probability 20% either one random event is removed (40%), moved (20%), or copied (40%).

Each training log contains 1000 traces that result from random walks through the configured model. Each test log and each base log contains 1000 traces. For every pair of a test log and a base log we determine for every trace from the test log whether it fits the discovered model better than the corresponding trace from the base log. 500 traces from the test log fit the original model better than the corresponding trace from the base log, and 500 do not. For sake of completeness: Two traces from both logs correspond if and only if they are at the same position in the corresponding logs: The *fifth *trace of the test log is classified against the *fifth* trace of the base log, etc.

## How, what and when to submit?

Please let Eric Verbeek know that you want to submit your implemented discovery algorithm. Eric will then provide you with a link where you can upload your submission.

You should submit a working discovery algorithm, which can be called using a “Discover.bat” Windows batch file which takes two parameters:

- The full path to the training log file,
**excluding**the “.xes” extension. - The full path to the model file where the discovered model should be stored,
**excluding**any extension like “.pnml”, “.bpmn”, or “.lsk”.

As an example, assuming that the miner discovers a Petri net,

Discover.bat logs\discovery\discovery-log models\discovered-model

will discover a model from the training log file “logs\discovery\discovery-log.xes” and will export the discovered Petri net to the file “models\discovered-model.pnml”.

If the results of calling your Discovery.bat file as described above is a PNML file (Petri nets), a BPMN file (BPMN diagram), or a LSK file (log skeleton), then you’re done. If not, the discovery algorithm needs to come with its own working classifier algorithm, that is, a “Classify.bat” Windows batch file, which takes four parameters:

- The full path to the test log file,
**excluding**the “.xes” extension. - The full path to the base log file,
**excluding**the “.xes” extension. - The full path to the model file which should be used to classify the test log,
**excluding**any extension like “.pnml”, “.bpmn”, or “.lsk”. - The full path to the log file where the classified test log should be stored,
**excluding**the “.xes” extension.

As an example, assuming that the miner discovered a Petri net,

Classify.bat logs\test\test-log logs\base\base-log models\discovered-model logs\classified\test-log

will classify whether every trace from the test log “logs\test\test-log.xes” fits the Petri net from “models\discovered-model.pnml” better than the corresponding trace from the base log “logs\base\base-log.xes” and it will export the classified traces (by adding the “pdc:isPos” attributes to every trace) as an event log in “logs\classified\test-log.xes”.

Classification of a trace is done by adding the boolean “pdc:isPos” attribute to the trace, which should be true if the trace is classified positive (fits your model better than the corresponding trace in the base model) and false if the trace is classified negative (does not fit your model better than the corresponding trace in the base model).

## Score and winners

For each training log, the “Discovery.bat” file is used to discover a model from the training log. Next, the “Classify.bat” is used to classify every trace in the test log against the corresponding trace in the base log using the discovered model. This results in a positive accuracy rate *P* and a negative accuracy rate *N* for this training log. From these, its F-score *F* is computed as 2*(*P***N*)/(*P*+*N*). The end score for the discovery algorithm is the *average F-score over all 480 training logs*.

The winner is the submission with the best end score.

## Key Dates

Submission Deadline | September 30, 2022 |

Disclosure of the Data Set | October 1, 2022 |

Winner Notification | October 7, 2022 |

Winner Announcement | During ICPM 20222 |

## Example discovery algorithms

We have run the three base miners on the data set: The Flower miner, the Directly Follows miner, and the Trace (or Sequence) miner.

### Flower miner

The Flower miner scores 0%, with a positive accuracy of 0.0% and a negative accuracy of 100.0%.

The Flower miner scores 0% as every trace fits the discovered model. As a result no trace fits better than another trace.

### Directly Follows miner

The Directly Follows miner scores 48%, with a positive accuracy of 35.7% and a negative accuracy of 94.3%.

### Trace miner

The Trace miner scores 90%, with a positive accuracy of 86.0% and a negative accuracy of 95.3%.