<?xml version="1.0" encoding="UTF-8"?>
<TEI xml:space="preserve" xmlns="http://www.tei-c.org/ns/1.0" 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
xsi:schemaLocation="http://www.tei-c.org/ns/1.0 https://raw.githubusercontent.com/kermitt2/grobid/master/grobid-home/schemas/xsd/Grobid.xsd"
 xmlns:xlink="http://www.w3.org/1999/xlink">
	<teiHeader xml:lang="en">
		<fileDesc>
			<titleStmt>
				<title level="a" type="main">Ebi -a Stochastic Process Mining Framework</title>
			</titleStmt>
			<publicationStmt>
				<publisher/>
				<availability status="unknown"><licence/></availability>
			</publicationStmt>
			<sourceDesc>
				<biblStruct>
					<analytic>
						<author role="corresp">
							<persName><forename type="first">Sander</forename><forename type="middle">J J</forename><surname>Leemans</surname></persName>
							<email>s.leemans@bpm.rwth-aachen.de</email>
							<affiliation key="aff0">
								<orgName type="institution">RWTH Aachen</orgName>
								<address>
									<country key="DE">Germany</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Tian</forename><surname>Li</surname></persName>
							<affiliation key="aff0">
								<orgName type="institution">RWTH Aachen</orgName>
								<address>
									<country key="DE">Germany</country>
								</address>
							</affiliation>
							<affiliation key="aff1">
								<orgName type="institution">University of Melbourne</orgName>
								<address>
									<country key="AU">Australia</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Jan</forename><surname>Niklas Van Detten</surname></persName>
							<affiliation key="aff0">
								<orgName type="institution">RWTH Aachen</orgName>
								<address>
									<country key="DE">Germany</country>
								</address>
							</affiliation>
						</author>
						<title level="a" type="main">Ebi -a Stochastic Process Mining Framework</title>
					</analytic>
					<monogr>
						<idno type="ISSN">1613-0073</idno>
					</monogr>
					<idno type="MD5">F07E6ABA3461262A0CECDBEF6625F528</idno>
				</biblStruct>
			</sourceDesc>
		</fileDesc>
		<encodingDesc>
			<appInfo>
				<application version="0.7.2" ident="GROBID" when="2025-04-23T16:32+0000">
					<desc>GROBID - A machine learning software for extracting information from scholarly documents</desc>
					<ref target="https://github.com/kermitt2/grobid"/>
				</application>
			</appInfo>
		</encodingDesc>
		<profileDesc>
			<textClass>
				<keywords>
					<term>Stochastic process mining</term>
					<term>stochastic process models</term>
					<term>event logs</term>
				</keywords>
			</textClass>
			<abstract>
<div xmlns="http://www.tei-c.org/ns/1.0"><p>Ebi is an open-source framework for stochastic process mining. Ebi currently contains over 30 techniques related to stochastic process mining, from completeness estimation to analysis, conformance checking, discovery, visualisation and statistical tests, and can be called from the command line.</p><p>For technique developers, Ebi allows abstractions on inputs through interfaces ("traits"), such that implemented techniques automatically support a variety of input and output types. Furthermore, Ebi almost completely uses exact arithmetic to avoid precision issues with low values.</p></div>
			</abstract>
		</profileDesc>
	</teiHeader>
	<text xml:lang="en">
		<body>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="1.">Introduction</head><p>Using process mining techniques, business analysts can find inefficiencies in business processes, with the ultimate aim of improving them. For efficient use of process improvement resources, it is important to recognise whether certain to-be-improved behaviour is frequent or rare. Such frequency information is referred to as the stochastic perspective in process mining, and techniques that take this stochastic information into account explicitly are called stochastic process mining techniques.</p><p>Stochastic process mining techniques are scattered across several process mining frameworks, such as Pm4py <ref type="bibr" target="#b0">[1]</ref>, BupaR <ref type="bibr" target="#b1">[2]</ref> and ProM <ref type="bibr" target="#b2">[3]</ref>, each with its strengths and weaknesses, ranging from computational efficiency to ease of applicability in high-performance computing settings.</p><p>None of these existing frameworks (i) allows a straightforward application of a particular technique to an input file, (ii) none is easily accessible from the command line, (iii) all require installation and external runtime environments and, most importantly, (iv) none support exact computations throughout.</p><p>Ebi is a command line utility focused on stochastic process mining techniques. For end users, it allows direct application of stochastic process mining techniques to files, and writes the output to a file. No need to import, click through options and export, or even to write scripts. In particular, Ebi supports exact computations, which are a necessity in stochastic process mining (see Section 2).</p><p>For developers, Ebi is a framework that allows abstractions on inputs through interfaces ("traits"), such that implemented techniques automatically support a variety of input and output types. Furthermore, Ebi provides the means to perform exact computations easily, through custom implementations of corresponding data structures and methods such as matrix computations, as well as solvers and optimisation routines. Ebi as a framework ensures a consistent parameter handling, and is thus well positioned to act as a background library for Pm4py, BupaR and ProM in the future. Ebi is open source and we welcome contributions from the community.</p><p>The remainder of this paper is organised as follows. In Section 2, we discuss the significance of Ebi for stochastic process mining. Section 3 details its innovations. Section 4 lists the currently implemented techniques, while Section 5 discusses its maturity and Section 6 concludes the paper.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="2.">Significance</head><p>In stochastic process mining, techniques may need to deal with astonishingly small numbers. For instance, the BPIC11 <ref type="bibr" target="#b3">[4]</ref> log has traces with more than 1 800 events. In any reasonable stochastic process model, the probability of such a trace would be well below 10 −300 , which is the minimum value that a double precision float can represent. Even if we could represent such low values reliably, doing any kind of computation would yield a low precision. For instance, if we want to compute the unit Earth-movers' stochastic conformance measure <ref type="bibr" target="#b4">[5]</ref>, we need to sum over one such value for each trace in the log, which would, in a typical log with thousands of traces, not leave any precision. In practice, computations on such logs without exact arithmetic would be highly unreliable. More numerically complex techniques that for instance require matrix computations like solving, inversion or multiplication with such low values would fare even worse. Hence, exact computations are a necessity in stochastic process mining, and Ebi is the first process mining framework that provides exact arithmetic for stochastic process mining.</p><p>Furthermore, having a command line interface eases the application of stochastic process mining techniques in demanding scientific experimental settings. Ebi is fully command-line based; though integrations with existing process mining frameworks such as Pm4py <ref type="bibr" target="#b0">[1]</ref>, BupaR <ref type="bibr" target="#b1">[2]</ref> and ProM <ref type="bibr" target="#b2">[3]</ref> are planned, in a similar fashion to Rust4pm <ref type="bibr" target="#b5">[6]</ref>.</p><p>Finally, Ebi encourages techniques to accept a large variety of inputs and produce a large variety of outputs, as it moves the burden of matching inputs and outputs of techniques to file types in the framework itself: by means of abstract interfaces (such as "a stochastic language that we can iterate over, and that iteration will end"), file types implement interfaces while techniques use them.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="3.">Innovations</head><p>Ebi aims to provide stochastic process mining techniques to analysts in a consistent and coherent fashion, accessible through the command line. The Ebi framework provides the following innovations:</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>• Background library &amp; command line</head><p>Ebi is a command line tool, which allows it to be applied easily in scientific experiment workflows. However, due to its structured set-up, it is well suited to be used as well as a fast background library for graphical tools or scripting languages such as Pm4py <ref type="bibr" target="#b0">[1]</ref>, BupaR <ref type="bibr" target="#b1">[2]</ref> and ProM <ref type="bibr" target="#b2">[3]</ref>.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>• Exact computation</head><p>As described in Section 2, exact computations are a necessity in stochastic process mining.</p><p>Completely transparent to end users and techniques, Ebi uses fractions of unlimited size, explicit logarithms and explicit roots to perform almost all computations exactly. However, exact computations can be disabled by the user for performance reasons. For more details, please refer to the manual. Unfortunately, most existing Rust libraries do not accept unlimited fractions as input, let alone explicit representations of logarithms and roots. Therefore, many secondary techniques, such as linear solvers, matrix computations and approximation techniques, were adapted to support exact computations.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>• Input and output detached from techniques</head><p>Completely transparent for end users, an implemented technique that needs to e.g. walk over the traces of an event log will automatically support all input formats for which that can be done. That is, techniques preferably define their inputs in terms of interfaces ("traits"). Again completely transparent to end users and techniques, the output of a technique is converted automatically by Ebi based on the file extension of the desired output file. For more details, please refer to the manual.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>• Local and memory-safe</head><p>Ebi runs locally and neither needs nor uses internet access, which makes it suitable for privacy-sensitive settings. Use of the Rust programming language ensures most types of memory-related errors are absent. Furthermore, Rust is, of course dependent on the programmer, more energy efficient than Java and much more energy efficient than Python <ref type="bibr" target="#b6">[7]</ref>.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="4.">Techniques, Files &amp; Architecture</head><p>In Ebi, a command is the implementation of an algorithm. As summarised in Figure <ref type="figure">1</ref>, a command defines the inputs it needs, in terms of traits and object types, as well its output type, in terms of an object type it will produce. For instance, the command will extract the most likely traces from its input. These inputs are (i) something that implements the FiniteStochasticLanguage or StochasticDeterministicSemantics trait, and (ii) an integer. When the user issues a command, Ebi will establish which traits and object types can serve as an input for the given command. For each of these traits and object types, Ebi will search which file handlers can provide it. For our example, the file handlers that can provide a usable input are a finite stochastic language (.slang), a compressed event log (.xes.gz), a stochastic labelled Petri net (.slpn), a stochastic deterministic finite automaton (.sdfa) and an event log (.xes). Ebi will attempt to load the given file with all of these file handlers, until it finds one that parses. Then, the command is executed. The command will result in an output, that is, an object of a particular object type. Then, Ebi will consider the file extension of the file the user wishes to write the result to, and see whether there is a file handler with that extension that can export the output object type. The main techniques for which Ebi currently provides an implementations are shown in Table <ref type="table">2</ref>. In total, Ebi currently has 30 commands. For a full overview of commands and their inputs and outputs, please refer to the manual, accessible through http://ebitools.org.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="5.">Maturity</head><p>Ebi has been used in the experiments described in several recent papers published by the author team <ref type="bibr" target="#b11">[12,</ref><ref type="bibr" target="#b14">15,</ref><ref type="bibr" target="#b15">16]</ref>. In these experiments, Ebi has shown to be me much faster than corresponding, earlier, implementations in other frameworks. This is presumably partly due to implementing these techniques a second time, though perhaps also due to the lower level access to computing</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="6.">Conclusion</head><p>Ebi is a framework for stochastic process mining. It offers exact arithmetic computation and, currently, over 30 algorithms related to stochastic process mining, ranging from completeness estimation to analysis, conformance checking, discovery, visualisation and statistical tests. For technique implementers, Ebi handles the input and output file handling: techniques only need to define their input and output format, and Ebi will take care of transformations automatically. Currently, Ebi is a command-line based tool, however, in future work, it is intended that Ebi can serve as a high speed background library for existing process mining frameworks such as BupaR, ProM and Pm4py.</p></div><figure xmlns="http://www.tei-c.org/ns/1.0" type="table" xml:id="tab_0"><head></head><label></label><figDesc>Architecture of Ebi.</figDesc><table><row><cell></cell><cell>export as</cell><cell></cell><cell cols="2">output as</cell><cell></cell><cell></cell></row><row><cell>handler file</cell><cell>imports</cell><cell>type object</cell><cell>implements</cell><cell>trait</cell><cell>input to</cell><cell>command</cell></row><row><cell></cell><cell></cell><cell></cell><cell></cell><cell>input to</cell><cell></cell><cell></cell></row><row><cell>Figure 1: Table 1</cell><cell></cell><cell></cell><cell></cell><cell></cell><cell></cell><cell></cell></row><row><cell>Files supported by Ebi.</cell><cell></cell><cell></cell><cell></cell><cell></cell><cell></cell><cell></cell></row><row><cell></cell><cell></cell><cell></cell><cell cols="3">extension(s) remarks</cell><cell></cell></row><row><cell>event log</cell><cell></cell><cell></cell><cell>.xes, .xes.gz</cell><cell></cell><cell></cell><cell></cell></row><row><cell cols="2">finite stochastic language</cell><cell></cell><cell>.slang</cell><cell></cell><cell></cell><cell></cell></row><row><cell>finite language</cell><cell></cell><cell></cell><cell>.lang</cell><cell></cell><cell></cell><cell></cell></row><row><cell cols="4">stochastic deterministic finite automaton .sdfa</cell><cell></cell><cell></cell><cell></cell></row><row><cell cols="2">stochastic labelled Petri net</cell><cell></cell><cell>.slpn</cell><cell></cell><cell></cell><cell></cell></row><row><cell>labelled Petri net</cell><cell></cell><cell></cell><cell>.lpn</cell><cell></cell><cell></cell><cell></cell></row><row><cell>accepting Petri net</cell><cell></cell><cell></cell><cell>.pnml</cell><cell cols="3">every deadlock is considered a final</cell></row><row><cell></cell><cell></cell><cell></cell><cell></cell><cell cols="2">marking</cell><cell></cell></row><row><cell>directly follows model</cell><cell></cell><cell></cell><cell>.dfm</cell><cell></cell><cell></cell><cell></cell></row><row><cell></cell><cell></cell><cell></cell><cell></cell><cell cols="3">Ebi analyse most-likely-traces</cell></row></table></figure>
		</body>
		<back>
			<div type="annex">
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Table 2</head><p>Techniques currently implemented in Ebi.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Technique command paper</head><p>Return all traces with their probabilities</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Ebi ana all</head><p>Estimate the completeness of an event log</p><p>Ebi ana comp <ref type="bibr" target="#b7">[8]</ref> Obtain the trace(s) that are on average the closest to all traces in an event log</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Ebi ana med</head><p>Get all traces that have a likelihood higher than a threshold</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Ebi ana minprob</head></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Get the most likely traces</head></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Ebi ana mostlikely</head><p>Align a finite (non-stochastic) language to a model Ebi anans ali <ref type="bibr" target="#b8">[9]</ref> ↣ computes alignments for any model, not just Petri nets Cluster traces into most-dissimilar groups (non-stochastic)</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Ebi anans clus</head><p>Obtain the trace(s) that are on average the closest to all traces in an event log (non-stochastic)</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Ebi anans med</head></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Association between process behaviour and trace attributes</head><p>Ebi asso atts <ref type="bibr" target="#b9">[10]</ref> Compute entropic relevance (uniform) Ebi conf er <ref type="bibr" target="#b10">[11]</ref> ↣ computes log-model comparisons for any model, not just SDFAs Compute Jensen-Shannon stochastic conformance Ebi conf jssc <ref type="bibr" target="#b11">[12]</ref> Compute unit earth-movers' stochastic conformance Ebi conf uemsc <ref type="bibr" target="#b4">[5]</ref> Convert stochastic languages and stochastic deterministic finite automata into other types</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Ebi conv …</head></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Discover a stochastic model using alignments</head><p>Ebi disc ali <ref type="bibr" target="#b12">[13]</ref> Discover a stochastic model using occurrences Ebi disc occ <ref type="bibr" target="#b12">[13]</ref> Discover a stochastic model by giving each transition a weight of 1 Ebi disc uni Print basic information on any file</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Ebi info</head><p>Compute the probability that a stochastic model will produce a trace of a specified language Ebi prob mod <ref type="bibr" target="#b13">[14]</ref> Compute the probability of a trace in a model Ebi prob trac <ref type="bibr" target="#b13">[14]</ref> Compute the most likely path a trace followed in a model</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Ebi prob exptra</head></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Sample a stochastic language</head></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Ebi sam</head><p>Test whether the sub-logs defined by a categorical trace attribute are derived from identical processes Ebi tst lcat <ref type="bibr" target="#b9">[10]</ref> Test-parse a file</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Ebi vali …</head></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Visualise as graph</head><p>Ebi vis svg resources that Rust provides; something also observed in the Rust4pm project <ref type="bibr" target="#b5">[6]</ref>. Furthermore, Ebi has proven to be much easier to integrate in a scientific experimental setting, due to its command-line interface: a simple command-line script suffices to perform complex chains of tasks, whereas in ProM or Pm4py, all file IO and intermediate-result storage, and all exceptions, need to be programmed. Finally, Ebi has been applied in several case studies with industry partners, including amongst other things in thesis projects.</p></div>			</div>
			<div type="references">

				<listBibl>

<biblStruct xml:id="b0">
	<monogr>
		<author>
			<persName><forename type="first">A</forename><surname>Berti</surname></persName>
		</author>
		<author>
			<persName><forename type="first">S</forename><forename type="middle">J</forename><surname>Van Zelst</surname></persName>
		</author>
		<author>
			<persName><forename type="first">W</forename><forename type="middle">M P</forename><surname>Van Der Aalst</surname></persName>
		</author>
		<idno>CoRR abs/1905.06169</idno>
		<title level="m">Process mining for python (pm4py): Bridging the gap between process-and data science</title>
				<meeting>ess mining for python (pm4py): Bridging the gap between process-and data science</meeting>
		<imprint>
			<date type="published" when="2019">2019</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b1">
	<analytic>
		<title level="a" type="main">bupar: Enabling reproducible business process analysis</title>
		<author>
			<persName><forename type="first">G</forename><surname>Janssenswillen</surname></persName>
		</author>
		<author>
			<persName><forename type="first">B</forename><surname>Depaire</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Swennen</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Jans</surname></persName>
		</author>
		<author>
			<persName><forename type="first">K</forename><surname>Vanhoof</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Knowl. Based Syst</title>
		<imprint>
			<biblScope unit="volume">163</biblScope>
			<biblScope unit="page" from="927" to="930" />
			<date type="published" when="2019">2019</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b2">
	<analytic>
		<title level="a" type="main">The prom framework: A new era in process mining tool support</title>
		<author>
			<persName><forename type="first">B</forename><forename type="middle">F</forename><surname>Van Dongen</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">ICATPN</title>
				<imprint>
			<publisher>Springer</publisher>
			<date type="published" when="2005">2005</date>
			<biblScope unit="volume">3536</biblScope>
			<biblScope unit="page" from="444" to="454" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b3">
	<monogr>
		<author>
			<persName><forename type="first">B</forename><surname>Van Dongen</surname></persName>
		</author>
		<title level="m">Real-life event logs -hospital log</title>
				<imprint>
			<date type="published" when="2011">2011</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b4">
	<analytic>
		<title level="a" type="main">Earth movers&apos; stochastic conformance checking</title>
		<author>
			<persName><forename type="first">S</forename><forename type="middle">J J</forename><surname>Leemans</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><forename type="middle">F</forename><surname>Syring</surname></persName>
		</author>
		<author>
			<persName><forename type="first">W</forename><forename type="middle">M P</forename><surname>Van Der Aalst</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">BPM Forum</title>
				<imprint>
			<publisher>Springer</publisher>
			<date type="published" when="2019">2019</date>
			<biblScope unit="volume">360</biblScope>
			<biblScope unit="page" from="127" to="143" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b5">
	<analytic>
		<title level="a" type="main">Rust4pm: A versatile process mining library for when performance matters</title>
		<author>
			<persName><forename type="first">A</forename><surname>Küsters</surname></persName>
		</author>
		<author>
			<persName><forename type="first">W</forename><forename type="middle">M P</forename><surname>Van Der Aalst</surname></persName>
		</author>
		<ptr target="CEUR-WS.org" />
	</analytic>
	<monogr>
		<title level="m">BPM Demos</title>
				<imprint>
			<date type="published" when="2024">2024</date>
		</imprint>
	</monogr>
	<note>to appear. to appear</note>
</biblStruct>

<biblStruct xml:id="b6">
	<analytic>
		<title level="a" type="main">Ranking programming languages by energy efficiency</title>
		<author>
			<persName><forename type="first">R</forename><surname>Pereira</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Couto</surname></persName>
		</author>
		<author>
			<persName><forename type="first">F</forename><surname>Ribeiro</surname></persName>
		</author>
		<author>
			<persName><forename type="first">R</forename><surname>Rua</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><surname>Cunha</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><forename type="middle">P</forename><surname>Fernandes</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><surname>Saraiva</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Sci. Comput. Program</title>
		<imprint>
			<biblScope unit="volume">205</biblScope>
			<biblScope unit="page">102609</biblScope>
			<date type="published" when="2021">2021</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b7">
	<analytic>
		<title level="a" type="main">Addressing the log representativeness problem using species discovery</title>
		<author>
			<persName><forename type="first">M</forename><surname>Kabierski</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Richter</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Weidlich</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">ICPM, IEEE</title>
				<imprint>
			<date type="published" when="2023">2023</date>
			<biblScope unit="page" from="65" to="72" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b8">
	<monogr>
		<title level="m" type="main">Conformance checking using cost-based fitness analysis</title>
		<author>
			<persName><forename type="first">A</forename><surname>Adriansyah</surname></persName>
		</author>
		<author>
			<persName><forename type="first">B</forename><forename type="middle">F</forename><surname>Van Dongen</surname></persName>
		</author>
		<author>
			<persName><forename type="first">W</forename><forename type="middle">M P</forename><surname>Van Der Aalst</surname></persName>
		</author>
		<imprint>
			<date type="published" when="2011">2011</date>
			<publisher>IEEE Computer Society</publisher>
			<biblScope unit="page" from="55" to="64" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b9">
	<analytic>
		<title level="a" type="main">Statistical tests and association measures for business processes</title>
		<author>
			<persName><forename type="first">S</forename><forename type="middle">J J</forename><surname>Leemans</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><forename type="middle">M</forename><surname>Mcgree</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Polyvyanyy</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><forename type="middle">H M</forename><surname>Hofstede</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">IEEE TKDE</title>
		<imprint>
			<biblScope unit="volume">35</biblScope>
			<biblScope unit="page" from="7497" to="7511" />
			<date type="published" when="2023">2023</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b10">
	<analytic>
		<title level="a" type="main">Entropic relevance: A mechanism for measuring stochastic process models discovered from event data</title>
		<author>
			<persName><forename type="first">H</forename><surname>Alkhammash</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Inf. Syst</title>
		<imprint>
			<biblScope unit="volume">107</biblScope>
			<biblScope unit="page">101922</biblScope>
			<date type="published" when="2022">2022</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b11">
	<analytic>
		<title level="a" type="main">The jensen-shannon distance metric for stochastic conformance checking</title>
		<author>
			<persName><forename type="first">T</forename><surname>Li</surname></persName>
		</author>
		<author>
			<persName><forename type="first">S</forename><forename type="middle">J J</forename><surname>Leemans</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Polyvyanyy</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">ICPM workshops</title>
				<imprint>
			<date type="published" when="2024">2024</date>
		</imprint>
	</monogr>
	<note>volume to appear of LNBIP</note>
</biblStruct>

<biblStruct xml:id="b12">
	<analytic>
		<title level="a" type="main">Stochastic process discovery by weight estimation</title>
		<author>
			<persName><forename type="first">A</forename><surname>Burke</surname></persName>
		</author>
		<author>
			<persName><forename type="first">S</forename><forename type="middle">J J</forename><surname>Leemans</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><forename type="middle">T</forename><surname>Wynn</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">ICPM Workshops</title>
				<imprint>
			<publisher>Springer</publisher>
			<date type="published" when="2020">2020</date>
			<biblScope unit="volume">406</biblScope>
			<biblScope unit="page" from="260" to="272" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b13">
	<analytic>
		<title level="a" type="main">Enjoy the silence: Analysis of stochastic petri nets with silent transitions</title>
		<author>
			<persName><forename type="first">S</forename><forename type="middle">J J</forename><surname>Leemans</surname></persName>
		</author>
		<author>
			<persName><forename type="first">F</forename><forename type="middle">M</forename><surname>Maggi</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Montali</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Inf. Syst</title>
		<imprint>
			<biblScope unit="volume">124</biblScope>
			<biblScope unit="page">102383</biblScope>
			<date type="published" when="2024">2024</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b14">
	<analytic>
		<title level="a" type="main">Stochastic process discovery: Can it be done optimally?</title>
		<author>
			<persName><forename type="first">S</forename><forename type="middle">J J</forename><surname>Leemans</surname></persName>
		</author>
		<author>
			<persName><forename type="first">T</forename><surname>Li</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Montali</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Polyvyanyy</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">CAiSE</title>
				<imprint>
			<publisher>Springer</publisher>
			<date type="published" when="2024">2024</date>
			<biblScope unit="volume">14663</biblScope>
			<biblScope unit="page" from="36" to="52" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b15">
	<monogr>
		<title level="m" type="main">Learning generalized stochastic petri nets from event data</title>
		<author>
			<persName><forename type="first">W</forename><forename type="middle">M</forename><surname>Van Der Aalst</surname></persName>
		</author>
		<author>
			<persName><forename type="first">S</forename><forename type="middle">J J</forename><surname>Leemans</surname></persName>
		</author>
		<editor>Festschrift Joost-Pieter Katoen</editor>
		<imprint>
			<date type="published" when="2024">2024</date>
		</imprint>
	</monogr>
	<note>to appear of LNCS</note>
</biblStruct>

				</listBibl>
			</div>
		</back>
	</text>
</TEI>
