1. Description
The UALSliceCollector actor collects a single time slice (specified by the "time" input port) of the input IDSs and copies it to a pulsefile with same shot but different run number. The copied slices are appended to existing slices in the output pulsefile, but more fine grained options are available (see Configuration). Only the slice of data from IDSs that are directed to this actor (input arrows) will be stored/appended to the output pulsefile.
Occurrence number associated with each IDS is numbered automatically, starting from 0 (default) for the first IDS (top-input port) of a given type, and increasing by one for each subsequent IDS of the same type. It means that the occurrence number of IDSs in the output run may be different than the one used in the workflow (for IDS stored in runwork pulsefile).
2. Ports
2.1. Inputs
You can add more input IDSs to this actor by using the "configure ports" option. Name of the port has no effect on the behavior of the actor as all the information associated with the IDS are stored within its record.
| port name | purpose | Icon |
|---|---|---|
machine | (optional) the output machine name. The default is the name of machine associated with the first input ids |  |
runout | run number for output pulse | |
time | time of the slice | |
ids | the IDS to be stored in output pulse |
2.2. Outputs
| port name | purpose |
|---|---|
error | error message after completion of UALSliceCollector "COPY IN DATABASE OK" in case UALSliceCollector finished succesfully |
3. Configuration
By default, UALSliceCollector opens the output pulsefile if it exists, and overwrites (calling put operation) existing data for IDSs listed as input when this actor is called the first time in the workflow. Subsequent calls will further append slices of data (putslice operation).
When the option "firstCreateParameter" is checked, UALSliceCollector will create the output pulsefile when the actor is called for the first time, hence ensuring that the pulsefile will contain no data stored previously.
When the option "firstPutNonTimedParameter" is un-checked, then the actor will directly append slice (operation putslice) to any existing data also at the first call in the workflow.
When un-checking "firstPutNonTimedParameter" you should make sure that the targeted IDSs have data already in the output pulsefile, as minimal non-timed (outside the slice) data like 'ids_properties.homogeneous_time' is mandatory for an IDS to be valid. This implies it makes no sense to check "firstCreateParameter" when "firstPutNonTimedParameter" is un-checked.
4. Version history
| version | description |
|---|---|