暫無描述

Yentl Van Tendeloo fc8ce0c724 Fixed read_info operation 7 年之前
bootstrap 9ce1af26bb Test the "types" operation 7 年之前
doc 005bdb59a3 Added some information about the returnvalue to the HTTP documentation 7 年之前
examples d41ae4e8b5 Fixed live modelling for CTCBD models 7 年之前
hybrid_server f516560d02 Fixed tests for model_add 7 年之前
integration 6f19274ab2 Permission updates 7 年之前
interface bd071b8d7e Safer way of finding an association destination and origin 7 年之前
kernel 2dbffc7b92 Make instantiate_node compiled 7 年之前
model 1c317d0b84 Revert "Merge branch 'DEVS' into testing" 7 年之前
models d41ae4e8b5 Fixed live modelling for CTCBD models 7 年之前
scripts 777d6063b3 Updated prompt script for fetching a taskname, instead of inventing one 7 年之前
services 27a3038e36 Updated two example scripts 7 年之前
state e480917c8f Implemented Modelverse Garbage Collection again (quite efficiently) 7 年之前
unit fc8ce0c724 Fixed read_info operation 7 年之前
wrappers fc8ce0c724 Fixed read_info operation 7 年之前
.gitattributes b3d374390d Make .gz files merge properly 8 年之前
.gitignore 0db83d0de7 Ignore temporary DEVS models 7 年之前
README.md 592282cbcf Massive cleanup 8 年之前

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