|Yentl Van Tendeloo 7014c3d695 Merge branch 'testing' of msdl.uantwerpen.be:yentl/modelverse into testing||6 months ago|
|bootstrap||6 months ago|
|doc||7 months ago|
|examples||6 months ago|
|hybrid_server||7 months ago|
|integration||7 months ago|
|interface||6 months ago|
|kernel||6 months ago|
|model||1 year ago|
|models||6 months ago|
|scripts||7 months ago|
|services||7 months ago|
|state||7 months ago|
|unit||7 months ago|
|wrappers||7 months ago|
|.gitattributes||2 years ago|
|.gitignore||10 months ago|
|New_MM.ipynb||6 months ago|
|README.md||1 year ago|
|example_integration.ipynb||6 months ago|
|notebook.ipynb||8 months ago|
|requirements.txt||7 months ago|
|tox.ini||7 months ago|
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 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.
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
After that, it will print out all the output of the Modelverse, and send in all your queries directly to the Modelverse.
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 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.
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.
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).
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: