Tools for the PNK Java version since v2.2:
||inaControl is a Petri Net Kernel application
for analysing Place/Transition Nets with the help of the Petri net
It only works together with the component
and with the
||PNVis supports the 3D-visualisation of a
system, that is modelled with a Petri net. To this end, the
Petri net modell is equipped with only some additional
information on the physical properties and and on the
continuous behaviour of the underlying system objects.
| LoLA frontend
|| This is a graphical user interface based on the
Petri Net Kernel for petri net analyzer tool LoLA.
It offers many features, like verifying deadlocks, bounded places,
dead transitions, reachability of a marking, etc. Furthermore it supports
||The Petri Net Cube is thought to support the abilities
of all standard net types using only one parameterized net type!!
Besides the PNC offers many features, like a step firing rule.
*) this tool needs Java3D to run
**) this tool needs the C-Compiler gcc to run
Components for the PNK Java version since v2.2:
|| This component can be used to load and save
those files to be read or written by the Petri net tool
INA is a tool package supporting the analysis of e.g.
What is the difference between tools and components?
In our manner of speaking a tool is not a single standalone
program as usual. A tool is a bigger package of many different files,
that can be integrated into the Petri Net Kernel. It can constist of different
net types & net type specifications, example nets, configuration files
and applications. A component is a kind of program or algorithm, that
can be integrated into the PNK and can be started from within the Application
Control. The component is bound on a petri net and can do some calculation
or manipulation on that net. There are some standard components, like
an editor or a general simulator, that come with the Petri Net Kernel.
A tool can consist of more than one component. Every tool has its own
tool specification, which represents a kind of connection between all
the different files, that come with the tool. The tool specification informs
the Petri Net Kernel about the components, net types and file formats,
that shall be used with that specific tool. If you want to use the Petri
Net Kernel with a certain tool, you have to start it with the corresponding
tool specification. The next chapter describes, how you can do this.
- Download the zip-file for your tool from the table above
- Copy the file into your PNK2.2 directory
- Unpack the archive (e.g. using "unzip <filename>")
- Read the README file that comes with the tool or component if there is any.
- Start the Petri Net Kernel with the tool calling the shell script,
that comes with the tool (e.g. "lola.sh"), or type:
java -jar <Jar archive of the tool> <tool specification>
If you are not sure about the name of the jar archive or the tool specification,
take a look at the shell script and simply type in the command, that
you find there.
You can find more information about a certain tool on our
The following Applications based on the Petri Net Kernel
exist for the PNK Python version:
|| with DAWN you can model and verify distributed
|| connnection between the INA -tool and the Petri Net Kernel
|| This application imports PEP files into the Petri Net Kernel. And, it exports PNK nets (or PNK
files) to PEP files. Graphical information of nets are transferable.
You developed a nice application based on the Petri Net
Kernel? You want it to be published here? Send an e-mail to:
Michael Weber - e-mail: email@example.com