Differences

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

--- musicode:start [2022/05/18 11:21] – [Changelog of Important MuPIF updates (in chronological order)] stanislavsulc
+++ musicode:start [2023/12/07 02:06] (current) – [Setting up Model Server] stanislavsulc
@@ Line 21: / Line 21: @@
 ==== MuPIF Services ====
-  * Platform online monitor  http://mupif.org/musicode/
+  * Platform online monitor http://mupif.org/musicode/
+  * Model API generator https://mupif.org/tools/api_generator.html
 ==== Changelog of Important MuPIF updates (in chronological order) ===
+. 1. 2022
   * Instead of PropertyID, FieldID, ParticleSetID, MiscID use only DataID, which contains all enum members
   * meatadata Inputs contain key "Set_at": {"type": "string", "enum": ["initialization", "timestep"]}, which defines whether it should be set before each timestep or only once at the initialization.
   * In initialize() function the argument "file" was removed. New methodology of setting input file using set() function and mupif.PyroFile, see https://github.com/mupif/mupif/blob/Musicode/examples/Example07-stacTM-JobMan-distrib/Example07.py.
   * Only generalized set() and get() functions can be used. Functions setProperty, getProperty, setField, getField, etc. are no longer supported.
+. 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.
@@ Line 49: / Line 56: @@
     ns=ns,
     appClass=ClassnameOfModel,
-    appName='Mupif.JobManager@model_name',
+    appName='InstitutionName.ModelName',
     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/Musicode/examples/Example13/server.py or other examples.
+After this script is executed, the jobmanager can be obtained from the nameserver by its name 'InstitutionName.ModelName'. 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/Musicode/examples/Example13/server.py or other examples.