説明なし

Yentl Van Tendeloo 1a35c8e7e9 Print JIT exceptions when detected for debugging 7 年 前
bootstrap 8831b563aa Work around some issues 7 年 前
doc 91e010a17a Fixed another problem with process enactment in documentation 7 年 前
hybrid_server 9c8799e980 Fixed "instruction pointer not found" error 7 年 前
integration 8831b563aa Work around some issues 7 年 前
interface 2a817aeb65 Remoded non-existing function 7 年 前
kernel 1a35c8e7e9 Print JIT exceptions when detected for debugging 7 年 前
model 1c317d0b84 Revert "Merge branch 'DEVS' into testing" 7 年 前
models a190d7d0d8 Try to print out all detected functions, while linking the main function 7 年 前
scripts 1b68fd2e8a Switch raw_input to input when needed. 7 年 前
services f746937885 Fixed some bugs related to AL models 7 年 前
state 7c5acc78fe Fixed test for MvS with new size of datatype 7 年 前
unit 8831b563aa Work around some issues 7 年 前
wrappers f62d8bb54c Merge branch 'master' into AL_print 7 年 前
.gitattributes b3d374390d Make .gz files merge properly 8 年 前
.gitignore 9a7fc2330d Merge branch 'testing' into MvK_rules 7 年 前
README.md 592282cbcf Massive cleanup 8 年 前
sum_times.py bfcb1fb5d4 More general code to sum times 8 年 前
test_printer.py 9c8799e980 Fixed "instruction pointer not found" error 7 年 前

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