Code repository for master thesis about example-driven DSML design http://msdl.cs.mcgill.ca/people/lucas

Lucas Heer e9e9031aff fixed verifying attributes of instance model: now an attribute is mandatory if all nodes of the same type have the same attribute 7 anni fa
bootstrap ef875e1f16 Fixed read_attrs 7 anni fa
doc 861f5c6c52 Update documentation for new activity execution 7 anni fa
evolution 7546bdf7cd also delete concrete syntax model when deleting node globally 7 anni fa
hybrid_server 8d26076636 Fixed "instruction pointer not found" error 7 anni fa
integration 8d0bcb1616 Work around some issues 7 anni fa
interface c730e25e10 Remoded non-existing function 7 anni fa
kernel 364bf7dffd New bootstrapping process: no more exec with initializers in a dictionary, but instead directly invoke the global assignment 7 anni fa
model 5e0500de3f Revert "Merge branch 'DEVS' into testing" 7 anni fa
models 5f30d83283 capture concrete syntax when typing a group and store it in a CS model 7 anni fa
scripts 8ca854edfc Switch raw_input to input when needed. 7 anni fa
services 39c849d8ef Fixed some bugs related to AL models 7 anni fa
sketchUI e9e9031aff fixed verifying attributes of instance model: now an attribute is mandatory if all nodes of the same type have the same attribute 7 anni fa
state 05bcbd450f Fixed test for MvS with new size of datatype 7 anni fa
unit 8d0bcb1616 Work around some issues 7 anni fa
wrappers e9e9031aff fixed verifying attributes of instance model: now an attribute is mandatory if all nodes of the same type have the same attribute 7 anni fa
.gitattributes b3d374390d Make .gz files merge properly 8 anni fa
.gitignore b219a79554 started on UI for instance modeling 7 anni fa
README.md 592282cbcf Massive cleanup 8 anni fa
alc_io.py ec9b3d7dd6 sync my files after latest merge from upstream, cleaned up a bit, adapted code to new exceptions 7 anni fa
alc_io.xml ec9b3d7dd6 sync my files after latest merge from upstream, cleaned up a bit, adapted code to new exceptions 7 anni fa
commons.py aff95fc175 reworked edge checking in verify code 7 anni fa
main.py edffd40bd9 implemented deleting model from UI 7 anni fa
sum_times.py bfcb1fb5d4 More general code to sum times 8 anni fa
test_printer.py 8d26076636 Fixed "instruction pointer not found" error 7 anni fa
upload_image_as_cs.py c1f1b1ccf9 added script to manually upload an image file as concrete syntax icon for a node, also finished fetching and displaying this image in UI 7 anni fa
verifier.py e9e9031aff fixed verifying attributes of instance model: now an attribute is mandatory if all nodes of the same type have the same attribute 7 anni fa

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