No Description

Yentl Van Tendeloo 2371f818ad Removed even more code: remove all jit specific folders completely 6 years ago
bootstrap 76f13745df Remove some more old JIT functions, which were available in the AL 6 years ago
doc b1f0de9b1d Update documentation for new activity execution 6 years ago
hybrid_server 2371f818ad Removed even more code: remove all jit specific folders completely 6 years ago
integration 8831b563aa Work around some issues 6 years ago
interface 76f13745df Remove some more old JIT functions, which were available in the AL 6 years ago
kernel 2371f818ad Removed even more code: remove all jit specific folders completely 6 years ago
model 1c317d0b84 Revert "Merge branch 'DEVS' into testing" 6 years ago
models c4c128ec38 Remove old comment of the new JIT in AL2PY code 6 years ago
scripts e9ffcef557 Updated the run_local_modelverse script to include the actual call file, making profiling possible 6 years ago
services d7c0452c93 Fix up exec. 6 years ago
state 923d13fe79 Sort formal parameters in export to resolve non-determinism in order 6 years ago
unit 8831b563aa Work around some issues 6 years ago
wrappers 2371f818ad Removed even more code: remove all jit specific folders completely 6 years ago
.gitattributes b3d374390d Make .gz files merge properly 7 years ago
.gitignore 9a7fc2330d Merge branch 'testing' into MvK_rules 6 years ago
README.md 592282cbcf Massive cleanup 6 years ago
run_pw.py a701d5f90d Added easier PW run test 6 years ago
sum_times.py bfcb1fb5d4 More general code to sum times 6 years ago
test_printer.py 6bc0a5a2e9 Merge branch 'testing' into new_JIT 6 years ago

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