Contact: Thomas Johnson, tjohn@kth.se.
Modelling real plasmas requires input from both the relevant experimental database and information about the machine hardware and settings. The purpose of the UalGetCpoBundle is to provide a workflow that reads both input CPOs related to the plasma state and the once that are related to the hardware. The workflow then bundles these CPOs into the CPOS-branch of the EU-ITM bundle. The target applications of this workflow is as an initialisation actor in workflows like the HCD workflow and the ETS.
The actor is still under development and need to be tested. So far only the wall, the nbi and the antennas CPOs are read from the machine description database, but more CPOs will be added (e.g. pfsystems and ironmodel). Note that the UalGetCpoBundle does not fill in the discharge related hardware settings. These have to be set externally with actors like the addECant, addICant and nbifiller.
The UalGetCpoBundle actor has a number of input ports, through which all input to the actor are passed. The list of input ports reads:
Port name | Datatype | Description |
---|---|---|
UserName | String | Name of the user whos UAL database we shall read from |
MachineName | String | Name of the machine (tokamak) used when accessing the UAL database |
ShotNumber | Integer | Shot number to be used when reading from the UAL database |
InputRunNumber | Integer | Run number to be used when reading the main CPOs from the UAL database |
TemporaryRunNumber_MainCpos | Integer | Run number used when the UALInit temporarily store the main CPOs during a run. Also referred to as runwork. |
TemporaryRunNumber_MachineDescriptions | Integer | Run number used when the UALInit temporarily store the Machine Description CPOs during a run. Also referred to as runwork. |
SelectMachineDescriptionCpos | Bundle |
Bundle of three boolean fields:
{use_MD_wall=True/False, use_MD_nbi=True/False, use_MD_antennas=True/False} The three field are used to select if the wall, the nbi and the antennas CPOs should be taken from the Machine Description Database or from the shot=ShotNumber and run=InputRunNumber. |
The UalGetCpoBundle-Workflow has been developed purely for the testing and development of the UalGetCpoBundle actor. This workflow (1) provides an interface for prescribing the input to be used by the UalGetCpoBundle actor and (2) it prints the output from the same actor.
To fill the input data double click on the composite actor at the top-level of the workflow. A box will then pop up where you can fill in each of the input parameters described above, as illustrated in figure 1. These parameters are then fed into the actor as illustrated in figure 2.
The UalGetCpoBundle actor, outlined in the figure 3 below, consists of four composite actors and some logic to connect these.
After the third actor there is a switch to determine which Machine Description data is requested and if we need any of the machine description CPO. If we do not, the output from UAL_read_main_CPOs will be sent to the output of the UalGetCpoBundle actor, othervise the third actor UAL_read_machine_description_CPOs is called.