...
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).
| Note |
|---|
Please note that input database will be read from: |
...
and |
...
and |
...
are specified as actor's parameters while |
...
will be created inside database pointed by |
...
environment variable (inside database of the user that is running the workflow). It is not possible to overwrite somebody else's data.
|
Ports
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) |
...
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
|
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.
Version history
| version | description |
|---|---|
| 3.0.4 | user and machine ports have to be connected at all times |