| Both sides previous revisionPrevious revisionNext revision | Previous revision |
| deema:start [2022/01/26 16:13] – bp | deema:start [2023/12/09 02:50] (current) – [MuPIF Services] stanislavsulc |
|---|
| * Platform online monitor http://mupif.org/deema/ | * Platform online monitor http://mupif.org/deema/ |
| * MuPIF database web interface: http://172.23.1.1:5555/ | * MuPIF database web interface: http://172.23.1.1:5555/ |
| * MuPIF RestAPI documentation: http://172.23.1.1:5000/help | * MuPIF RestAPI documentation: http://172.23.1.1:8005/docs |
| |
| ==== Using MuPIF Web API ==== | ==== Using MuPIF Web API ==== |
| * 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 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 "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) === |
| | |
| | 9. 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"] |
| | |
| | 18. 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. |
| |
| |
