No Description

Yentl Van Tendeloo ae577b488e Added PM to FTG transformation 3 years ago
bootstrap 841487fc80 Remove unnecessary prints 3 years ago
doc e84213d6b6 Add reference to examples folder 3 years ago
examples ae577b488e Added PM to FTG transformation 3 years ago
hybrid_server 76f632cb30 Don't do a GC run at startup 3 years ago
integration fc3388d1e5 patched unit tests 3 years ago
interface 57b95d3ebb Working conformance check for AToMPM (multi-inheritance part) 3 years ago
kernel b65182b94d Fixed sort algorithm 3 years ago
model 1c317d0b84 Revert "Merge branch 'DEVS' into testing" 4 years ago
models ae577b488e Added PM to FTG transformation 3 years ago
scripts 5e501065c0 Fix stacktracer error 3 years ago
services d49fcd16a8 Add in DEVS debugger 3 years ago
state e480917c8f Implemented Modelverse Garbage Collection again (quite efficiently) 3 years ago
unit 841487fc80 Remove unnecessary prints 3 years ago
wrappers ae577b488e Added PM to FTG transformation 3 years ago
.gitattributes b3d374390d Make .gz files merge properly 4 years ago
.gitignore 0db83d0de7 Ignore temporary DEVS models 3 years ago 592282cbcf Massive cleanup 4 years 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/