Нема описа

Yentl Van Tendeloo 0f00626510 Fixed some minor bugs and performance issues in entry ID retrieval пре 7 година
bootstrap 0f00626510 Fixed some minor bugs and performance issues in entry ID retrieval пре 7 година
doc 396175dcbf Updated the wrappers documentation for hierarchy as well пре 8 година
hybrid_server 07186486e5 Fix garbage collect call пре 8 година
integration 43ed4f3d2e Fixed powerwindow debug пре 7 година
interface 3c1db73f4e Update interface of plot renderer пре 7 година
kernel f1291cdcc7 Slightly more readable code to invoke the JIT пре 7 година
model b2f0bc0469 Naively changed user to task in all files пре 8 година
models 348afda676 Updated model_overwrite: only the megamodelling version remains, and explicitly takes the required metamodel пре 7 година
scripts daa9a291fe Semi-working transformation_execute and transformation_add пре 7 година
services d4c2dcb649 Remove the unnecessary sleep in most services пре 7 година
state 990561a052 Added a rudimentary form of None... пре 7 година
unit 683eb4fc53 Preliminary working version of parallel process enactment пре 7 година
wrappers fb88f800b9 Fix error in model_overwrite пре 7 година
.gitattributes b3d374390d Make .gz files merge properly пре 8 година
.gitignore 30c4d323bd Ignore the .tmp files in Git пре 7 година
README.md 592282cbcf Massive cleanup пре 8 година
sum_times.py bfcb1fb5d4 More general code to sum times пре 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