Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

IMAS actorDescription
UALInit

Initializes input pulse file, creates run work and provides IDS description for other actors

inputs:

    • user - name of the user for input data file (e.g. g2michal)
    • machine - name of the machine for input data file (e.g. test/jet)
    • shot - shot number
    • run - run number
    • runwork - temporary run number (place where output will be stored)

outputs:

    • error - description of error in case there are problems while accessing input data
    • all IDSess requested by user (each IDS is specified as output port name)
UALCloseCloses run work based on description passed via input IDS.
UALCollectorStores input IDSess inside new run. This way, it is possible to copy data into different shot/run rather than inside run work.
UALSliceCollectorStore one slice from input IDS into different run. This way, it is possible to collect intermediate results during workflow execution.
UALMux

Provides a method for putting data inside IDS

inputs:

    • inputIds/inputCpo - cpo we are going to modify
    • inTime - time index at which data are supposed to be updated
    • name of the field is specified as port name
    • new value of the field is passed as value sent to the port

outputs:

    • outputIds/outputCpo - modified IDS
    • outTime - actual time index (depend on approximation mode)
UALMuxParam

Provides similar behavior to ualmux/UALMux, however, this actors has two additional ports:

    • fieldDescription - contains name of the filed that will be modified
    • fieldValue - contains new value of the field

Main difference between ualmux/ualmuxparam actors lays in it's ability to be used in a loop that modify different field inside IDS.

You can simply provide different field name for different loop's step.

UALDemuxAllows to read data from given IDS - name of the field is specified as output port.
UALPython

Allows to run external Python process and pass input/output data between workflow and process itself. This actor is, most commonly, used for data visualization.

User can pass Python script directly to the actor.

SetBreakpointThis actor allows to enforce "debug" mode for IMAS /ITM based actors. It sets global parameter "ITM_DEBUG" to either true or false. In case true is a value of "ITM_DEBUG" all FC2K generated actors will start in debug mode.
IDSOccurenceProvides a method to create duplicate of IDS with new occurrence number. This way, it is possible to store data before they get modified by user code.
IDSFlushFlushes data from workflow. Data from memory cache are stored inside database.
IDSDiscardDiscards data inside workflow. Data will be re-read into memory cache.
IDSContentDisplays IDS data.