Ingen beskrivning

Yentl Van Tendeloo 4dd33101a0 Many optimizations to the request handler and number of calls 7 år sedan
bootstrap 1bce8f0e46 Fix several issues with output; introduce new "FINISH" opcode 7 år sedan
doc b1f0de9b1d Update documentation for new activity execution 7 år sedan
hybrid_server b3487abe8f Rewrite request_handler from scratch 7 år sedan
integration 8831b563aa Work around some issues 7 år sedan
interface 76f13745df Remove some more old JIT functions, which were available in the AL 7 år sedan
kernel 4dd33101a0 Many optimizations to the request handler and number of calls 7 år sedan
model 1c317d0b84 Revert "Merge branch 'DEVS' into testing" 7 år sedan
models c4c128ec38 Remove old comment of the new JIT in AL2PY code 7 år sedan
scripts 5e501065c0 Fix stacktracer error 7 år sedan
services 5fac9c6fff Change nicer termination behaviour without tons of stacktraces 7 år sedan
state 313e8f94c1 Optimize accesses to globals: cache for each task individually 7 år sedan
unit 5fac9c6fff Change nicer termination behaviour without tons of stacktraces 7 år sedan
wrappers 4dd33101a0 Many optimizations to the request handler and number of calls 7 år sedan
.gitattributes b3d374390d Make .gz files merge properly 8 år sedan
.gitignore 9a7fc2330d Merge branch 'testing' into MvK_rules 7 år sedan
README.md 592282cbcf Massive cleanup 8 år sedan
run_pw.py 0e48e93215 Fixed PM enactment code from set to list (for double enactment of e.g., join) 7 år sedan
sum_times.py bfcb1fb5d4 More general code to sum times 8 år sedan
test_printer.py 6bc0a5a2e9 Merge branch 'testing' into new_JIT 7 år sedan

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