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

Yentl Van Tendeloo b5959a2a33 Working AL to PY again, but now with correct variable names il y a 7 ans
bootstrap b5959a2a33 Working AL to PY again, but now with correct variable names il y a 7 ans
doc 282797d2ef Fixed another problem with process enactment in documentation il y a 7 ans
hybrid_server 8d26076636 Fixed "instruction pointer not found" error il y a 7 ans
integration 2ff4edee6b Merge remote-tracking branch 'bentley/master' into testing il y a 7 ans
interface c730e25e10 Remoded non-existing function il y a 7 ans
kernel f87effbef9 Debugging... switch to desktop il y a 7 ans
model 5e0500de3f Revert "Merge branch 'DEVS' into testing" il y a 7 ans
models b5959a2a33 Working AL to PY again, but now with correct variable names il y a 7 ans
scripts 8ca854edfc Switch raw_input to input when needed. il y a 7 ans
services 39c849d8ef Fixed some bugs related to AL models il y a 7 ans
state 8d26076636 Fixed "instruction pointer not found" error il y a 7 ans
unit 378dfae703 Fix import and allow piece-by-piece testing. il y a 7 ans
wrappers b5959a2a33 Working AL to PY again, but now with correct variable names il y a 7 ans
.gitattributes b3d374390d Make .gz files merge properly il y a 8 ans
.gitignore a804676c3b Merge branch 'testing' into MvK_rules il y a 7 ans
README.md 592282cbcf Massive cleanup il y a 8 ans
sum_times.py bfcb1fb5d4 More general code to sum times il y a 8 ans
test_printer.py 8d26076636 Fixed "instruction pointer not found" error il y a 7 ans

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