Code repository for master thesis about example-driven DSML design http://msdl.cs.mcgill.ca/people/lucas

Yentl Van Tendeloo 79a0f5bc78 Recompile log_output, which broke tests for some reason 7 gadi atpakaļ
bootstrap 697179ac22 Revert "Preliminary support for spawning a new task to a specific function" 7 gadi atpakaļ
doc 396175dcbf Updated the wrappers documentation for hierarchy as well 8 gadi atpakaļ
hybrid_server 07186486e5 Fix garbage collect call 7 gadi atpakaļ
integration e56bbdf958 PM execution takes a dictionary for binding 7 gadi atpakaļ
interface 697179ac22 Revert "Preliminary support for spawning a new task to a specific function" 7 gadi atpakaļ
kernel 8d33a644ff Patched "Could not process break statement" bug 7 gadi atpakaļ
model b2f0bc0469 Naively changed user to task in all files 8 gadi atpakaļ
models 56c6f79c23 Working initial version of PDEVS simulation as a service 7 gadi atpakaļ
scripts aa1b8a8103 Auto-detect all services to execute 7 gadi atpakaļ
services 56c6f79c23 Working initial version of PDEVS simulation as a service 7 gadi atpakaļ
state 990561a052 Added a rudimentary form of None... 7 gadi atpakaļ
unit 79a0f5bc78 Recompile log_output, which broke tests for some reason 7 gadi atpakaļ
wrappers 79a0f5bc78 Recompile log_output, which broke tests for some reason 7 gadi atpakaļ
.gitattributes b3d374390d Make .gz files merge properly 8 gadi atpakaļ
.gitignore ab32b39f3a Ignore the .tmp files in Git 7 gadi atpakaļ
README.md 592282cbcf Massive cleanup 8 gadi atpakaļ
sum_times.py bfcb1fb5d4 More general code to sum times 8 gadi atpakaļ

README.md

Installation

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/run_local_modelverse.py 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/prompt.py. 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/modelverse.py, and provides Python functions that make the necessary Modelverse requests. At the moment, not all functions are implemented in the wrapper yet.

Performance

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.

Tests

Running the tests is easy: simply execute scripts/run_tests.py 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:

wget https://msdl.uantwerpen.be/files/get-pip.py
pypy get-pip.py --user
pypy -m pip install pytest --user

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

pypy scripts/run_tests.py