No Description

Yentl Van Tendeloo 7014c3d695 Merge branch 'testing' of into testing 6 months ago
bootstrap 48d70a2c90 Fixes for PN and CTCBD and DTCBD transformations 6 months ago
doc 9840b07033 Added note about local functions not working on Windows due to Python implementation issues. 7 months ago
examples 7014c3d695 Merge branch 'testing' of into testing 6 months ago
hybrid_server 3834f6e351 Add profiling functionality 7 months ago
integration 2ec870d4fd Patched up the remainder of the Power Window for Windows 7 months ago
interface 67bb9b16cd Fixed invalid process models 6 months ago
kernel 48d70a2c90 Fixes for PN and CTCBD and DTCBD transformations 6 months ago
model 1c317d0b84 Revert "Merge branch 'DEVS' into testing" 1 year ago
models 48d70a2c90 Fixes for PN and CTCBD and DTCBD transformations 6 months ago
scripts cb9beb4604 Add script to analyse profiling results 7 months ago
services b93bdf64d6 Remove prints 7 months ago
state 4f9b277bec Use marshal instead of Pickle for the MvS 7 months ago
unit e898f1b5b4 Fixes for Windows 7 months ago
wrappers 547702e08d Fix Python 3 compatibility 7 months ago
.gitattributes b3d374390d Make .gz files merge properly 2 years ago
.gitignore 0db83d0de7 Ignore temporary DEVS models 10 months ago
New_MM.ipynb 89c94ea60e Re-add processing of input/output to the AL for our own FSA 6 months ago 592282cbcf Massive cleanup 1 year ago
example_integration.ipynb 5b3e3fc617 Added semantics to the notebook 6 months ago
notebook.ipynb 330fe37bf3 Fix bootstrap file not being properly uploaded 8 months ago
requirements.txt 89404372d2 Add requirements.txt for easy installation of dependencies, and a tox file 7 months ago
tox.ini 55e52d0537 Add more interpreters to Tox 7 months ago


Installing the Modelverse is unnecessary, as it is mere Python code and doesn't use installation scripts. All scripts which are generally useful are found in the 'scripts' directory, and are written in OS-independent Python code.

You will, however, need to install a dependency: the SCCD compiler and runtime.

Starting up the Modelverse

Starting up the Modelverse is easy: simply execute the scripts/ script, with as parameter the port you want to use. By default, port 8001 is used.

Communicating with the Modelverse

Now that the Modelverse is running, you will want to communicate with it! To do this, you can use whatever tool you want, as long as it can send and receive XML/HTTPRequests. For example, a mere internet browser can already communicate with the Modelverse, though not in the most user-friendly way.

A nicer way is through the Python prompt script scripts/ After that, it will print out all the output of the Modelverse, and send in all your queries directly to the Modelverse.

Python wrapper

To automatically communicate with the Modelverse in a programmatic way, a Python wrapper is provided. This wrapper is found in wrappers/, and provides Python functions that make the necessary Modelverse requests. At the moment, not all functions are implemented in the wrapper yet.


Performance of the Modelverse is currently rather low. This is primarily caused by the reliance on the action language, which is an explicitly modelled (and interpreted) language. Additionally, the Modelverse runs remotely, meaning that all requests have to pass over the network. Even when this is executed on the same machine, this causes quite some overhead.

Additional documentation

Some additional documentation can be found online in the Modelverse techreport, describing the internal workings of the Modelverse, as well as a brief introduction on how to use it. There is also in-depth documentation describing how to use the Modelverse and its various languages.


Running the tests is easy: simply execute scripts/ in the main modelverse folder. This will invoke the necessary build commands (to create bootstrapping code etc.) and call the tests for each individual aspect of the Modelverse. Note that testing is done using py.test, which is the only dependency of the Modelverse (and only for tests, of course).

Using PyPy

Since all scripts chain the invocation with the same interpreter as originally invoking the script, you will need to install py.test for PyPy. Assuming that you already have PyPy installed, you can simply install py.test using these commands:

pypy --user
pypy -m pip install pytest --user

From then on, you can simply invoke all tests in PyPy using:

pypy scripts/