Home Verkennen Help
Inloggen
lucas
/
modelverse
geforked van yentl/modelverse
Volgen 1
Ster 0
Vork 0
Bestanden
Boom: 98876ddc3c
Aftakkingen Labels
modelverse
/
doc
/
interaction.rst

interaction.rst 2.1 KB
Geschiedenis Ruwe

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748 
  1. Basic Interaction
    2. 

  2. =================
    3. 

  3. 

  4. As previously mentioned during the installation phase, the Modelverse is merely a collection of scripts.
    5. 

  5. We briefly present how the Modelverse is structured, and introduce the most important scripts for general use.
    6. 

  6. A more elaborate view on the architecture and the different scripts is only required for developers of the Modelverse.
    7. 

  7. 

  8. Simplified Architecture
    9. 

  9. -----------------------
    10. 

  10. 

  11. The Modelverse architecture consists of three core concepts, which will be referred to throughout the documentation.
    12. 

  12. 

  13. Modelverse State (MvS)
    14. 

  14. ^^^^^^^^^^^^^^^^^^^^^^
    15. 

  15. 

  16. The Modelverse State (MvS) is the memory of the Modelverse, and contains all data pertaining to it.
    17. 

  17. This includes not only the different models created by the users, but also all metamodels, transformations, operations, but also all bootstrap files.
    18. 

  18. Furthermore, it includes all execution state of operations being executed in the Modelverse.
    19. 

  19. As such, the Modelverse State is the database of the Modelverse, which is the only component containing data.
    20. 

  20. Only developers will ever have to directly interface with the Modelverse State.
    21. 

  21. 

  22. Modelverse Kernel (MvK)
    23. 

  23. ^^^^^^^^^^^^^^^^^^^^^^^
    24. 

  24. 

  25. The Modelverse Kernel (MvK) is the execution core of the Modelverse, and connects to the Modelverse State to fetch the instructions to execute.
    26. 

  26. All its execution information is stored in the MvS as well, and therefore it has to (theoretically) query the MvS for each and every instruction.
    27. 

  27. It merely consists of a set of model transformation rules which take the current state of the MvS, and do a set of modifications on it.
    28. 

  28. Only developers will ever have to directly interface with the Modelverse Kernel.
    29. 

  29. 

  30. Modelverse Interface (MvI)
    31. 

  31. ^^^^^^^^^^^^^^^^^^^^^^^^^^
    32. 

  32. 

  33. The Modelverse Interface (MvI) ...
    34. 

  34. 

  35. Necessary scripts
    36. 

  36. -----------------
    37. 

  37. 

  38. Explain the different scripts and how they can be used
    39. 

  39. Briefly show the *run_tests.py* and *run_local_modelverse.py*
    40. 

  40. Also *prompt.py*
    41. 

  41. 

  42. Wrapper
    43. 

  43. -------
    44. 

  44. 

  45. We explain the simple Python wrapper
    46. 

  46. Other wrappers can be defined quite easily due to the Modelverse architecture
    47. 

  47. Later is a full overview of the wrapper, we now introduce it piece by piece in Python
    48. 

  48.