1. Description
UALInit actor is responsible for reading input data (pulse file) and storing requested IDSes inside so called run work. Once run work is created all data access related actions are performed on this file. It means that initial data are never affected by Kepler (you can't accidentally overwrite them, unless you explicitly use the input file as output - e.g. UALCollector or UALSliceCollector).
Please note that input database will be read from: user and machine - where user and machine are specified as actor's parameters while runwork will be created inside database pointed by $USER environment variable (inside database of the user that is running the workflow). It is not possible to overwrite somebody else's data.
As input pulse 'machine' is used for runwork pulse, the database layout for this 'machine' entry should exist in the local user space ($USER/public/imasdb) before calling the actor. As a reminder, you can simply create such layout for a new machine by executing the command imasdb machine
2. Ports
2.1. Inputs
| port name | purpose | Icon |
|---|---|---|
user | name of the user - data will be read from this user's public database |  |
machine | name of the tokamak (take a look at imasdb tool) | |
shot | shot number | |
run | run number | |
runwork | temporary run number (where intermediate data are stored) |
2.2. Outputs
UALInit actor allows you to specify names of the IDSes that will be used during computation. For each IDS you want to use during workflow execution, you have to specify it as output port. Right-click actor and choose Configure ports. Once configuration dialog is open, press Add and type in the name of the IDS you want to use during computations. Make sure to check Output for the type of port. In sample below we use summary IDS.
In case you want to use different occurrence number, make sure to specify it in port name using ids/occurrence convention, e.g.: equilibrium/1.
| port name | purpose |
|---|---|
error | error message after completion of |
3. Configuration
UALInit can be run in so called Memory Cache regime. In case Memory Cache is used, all data are stored only inside memory - there is no intermediate data storage (apart from few exceptions). This will speed up execution of actor, but also limit some functionality (e.g. accessing data from the external processes - e.g. visualisation of intermediate results). To enable Memory Cache, right-click actor and choose Configure.
4. Version history
| version | description |
|---|---|
| 3.0.4 | user and machine ports have to be connected at all times |