You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

1. Kepler - ITM vs. IMAS

Kepler installation for IMAS and ITM environments consists (mainly) of two sets of actors:

  • ITM: Kepler 2.4/2.5 based installation + custom ITM actors
  • IMAS: Kepler 2.4/2.5 based installation + custom IMAS actors

Whenever you start Kepler at Marconi Gateway you can choose between one of two releases. Each of them is able to use underlaying data access layer. Below, you can take a brief look at most recent used actors available for both platforms.

You can easily spot similarities in both sets. Each ITM based actor has corresponding IMAS based actors. Behavior of these actors is very similar. They simply operate on different data sets.

ITMIMAS
ITM actorIMAS actorDescription
ualinitUALInit

Initializes input pulse file, creates run work and provides CPO/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 IDSes/CPOs requested by user (each IDS/CPO is specified as output port name)
   
   
   
   
   
   
   
   
   
   
   
   
  • No labels