Differences

This shows you the differences between two versions of the page.

--- deema:start [2021/12/20 06:32] – stanislavsulc
+++ deema:start [2023/12/09 02:50] (current) – [MuPIF Services] stanislavsulc
@@ Line 22: / Line 22: @@
   * Platform online monitor  http://mupif.org/deema/
   * MuPIF database web interface: http://172.23.1.1:5555/
+  * MuPIF RestAPI documentation: http://172.23.1.1:8005/docs
 ==== Using MuPIF Web API ====
-  * In the web interface in the list of workflows (http://172.23.1.1:5555/workflows) there is a workflow with wid "workflow_13" - click on the link to go to its detail (or click here: http://172.23.1.1:5555/workflows/workflow_13). The page shows the inputs and outputs of this workflow and a link to create a new execution - click on the "Initialize new execution record" and you get to the created execution's detail. Click on "Set inputs and Task_ID" and submit the imput data. This workflow assumes that we provide two numbers in the form of a tuple - for submitting values 3.0 and 2.5 fill in "(3.0,)" and "(2.5,)". After saving by clicking on "Submit" you can get back to execution record by clicking on the displayed link. Now you can click on the "Schedule execution", which should change the status from "Created" to "Pending". After some time (scheduler checks new executions in 1 minute period) you can refresh this page and check if the status is "Finished". If so, click on the "Discover outputs" to see the results of this simple calculation.
+  * Using of the web interface is demonstrated on a simple workflow, which already exists in the MuPIF database. In the list of workflows (http://172.23.1.1:5555/workflows) there is this workflow with wid "workflow_13" - click on the link to go to its detail (or click here: http://172.23.1.1:5555/workflows/workflow_13). The page shows the inputs and outputs of this workflow and a link to create a new execution - click on the "Initialize new execution record" and you get to the created execution's detail. Click on "Set inputs and Task_ID" and submit the imput data. This workflow assumes that we provide two numbers. After saving by clicking on "Submit" you can get back to execution record by clicking on the displayed link. Now you can click on "Schedule execution", which should change the status from "Created" to "Pending". After some time (scheduler checks new executions in 30 second period) when the simulation finishes or fails, the page reloads. If the status is "Finished", click on the "Discover outputs" to see the results of this simple calculation.
+==== Changelog of Important MuPIF updates (in chronological order) ===
+. 2. 2022
+  * Obj_ID in Inputs/Outputs metadata must be of type string.
+  * For Type mupif.Property in Inputs/Outputs metadata the "ValueType" must be specified. Choose from following values: ["Scalar", "Vector", "Tensor"]
+. 5. 2022
+  * The workflow metadata contain item "Models" to describe the instantiation of the contained models. (jobmanager name for remote model and module name with class name for local model) See MuPIF examples. The models are instantiated automatically by the workflow, so there is no need to implement it in the initialize method.
+  * The default value of metadata argument in the initialize function was changed to None.
 ==== Setting up Model Server ====
+Assuming we have a properly implemented model class named 'ClassnameOfModel', which is derived from mupif.Model and is implemented in file 'model_example.py', we can make it accessible from the Deema VPN network with the following script. First we import mupif and the model class
+<code>
+import mupif as mp
+from model_example import ClassnameOfModel
+</code>
+Then we locate the nameserver with
+<code>
+ns = mp.pyroutil.connectNameServer(nshost='172.23.1.1', nsport=10000)
+</code>
+Then the script contains a code, which creates a jobmanager instance with given parameters, runs it and registers it on the nameserver. The maxJobs is an optional parameter specifying how many remote model instances can exist at the same time.
+<code>
+mp.SimpleJobManager(
+    ns=ns,
+    appClass=ClassnameOfModel,
+    appName='Mupif.JobManager@model_name',
+    jobManWorkDir='directory_path',
+    maxJobs=5
+).runServer()
+</code>
+After this script is executed, the jobmanager can be obtained from the nameserver by its name 'Mupif.JobManager@model_name'. With the jobmanager we can remotely instantiate a new instance of our model class. For more information look at the https://github.com/mupif/mupif/blob/Deema/examples/Example13/server.py or other examples.
+==== Interaction with test jobmanager ====
+An existing jobmanager "CVUT.demo01" for model from mupif Example13 (https://github.com/mupif/mupif/tree/Deema/examples/Example13) is running and is registered at the project nameserver, which can be seen in the monitor at http://mupif.org/deema/. To run the workflow in https://github.com/mupif/mupif/blob/Deema/examples/Example13/main.py, which interacts with the this existing jobmanager, run the following command in the Example13 directory:
+<code>
+MUPIF_NS=172.23.1.1:10000 python3 main.py
+</code>
+It asks the given nameserver for the jobmanager named "CVUT.demo01", which provides a new instance of the model, which it then used for the calculation.
+==== Getting Help ====
+  * The preferred way to get support from CVUT Team is to create a new ticket on GitHub (https://github.com/mupif/mupif/issues). This way you can track progress of your issue and get support quckly.