Repo holding scripts for interacting with ProM using CLI and testing the invoking of ProM from an external program.
From the official website of the ProM project:
ProM is an extensible framework that supports a wide variety of process mining techniques in the form of plug-ins. It is platform independent as it is implemented in Java, and can be downloaded free of charge.
Maybe you would want to
... run process mining analyses on several logs in batch mode without user interaction.
as quoted from a blog post by Dirk Fahland.
-
Or it could be that you want to have some of your own programs working in synergy with ProM but you don't know Java that much.
-
Or simply because that a sexy Graphical User Interface is brilliant but is not for everyone.
A fresh download of ProM does not contain even those basic ones (meaning that it could fail in invoking functions like open_xes_log_file). Make sure that you have already run ProM (via GUI) and have solved those basic dependencies (Runner up packages) using ProM PM before you get too excited about the CLI hack.
In other words, it seems impossible to get CLI worked from the very beginning, which could pose some challenges if one wants to do all these on a server without GUI and using a fresh download.
There could be ways to solve those dependencies through CLI but unfortunately I haven't been able to figure them out. My best guess is to do it through an initial script that invokes a series of functions to fetch the first several packages to the local library.
The main script ProM69_CLI.sh was developed for the only purpose of storing the shell commands and thus to be used as a shortcut entry for invoking the CLI feature. It was written for Linux OS and ProM 6.9, however producing one for MS Windows or other versions of ProM would be trivial.
The script was produced by altering a variable in the shell script provided by ProM, as instructed in Dirk Fahland's blog post.
Note that it is not the place where you would like to put your hacking codes in --- they should be written in a separate text file. In this repo I put those transaction codes in files with .java extensions.
To get things running, you will need to
- Put the main script under your ProM root directory, i.e, where configuration files like
ProM.iniare; - Change working directory to your ProM root directory;
- Write your own scripts as these .java files, and execute them by using the following shell command:
username@hostname:[your_ProM_root_dir]$ sh ProM69_CLI.sh -f [path_to_your_script]This project is motivated by an issue that I have encountered in my own research, and is largely inspired by Dirk Fahland's blog post (see above) as well as a number of posts from the ProM forum.
Note that this project is for experimental use and does not guarantee any unplanned functionalities, software code compliance or any future maintenance.