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

Compare with Current View Page History

« Previous Version 5 Next »

1. Issues

1.1. General

To access every machine I have to use separate configuration:

  • There is no single plugin installation that can handle all machines
  • There is no common installation of AL that works fine with all plugins

1.2. Runtime errors:

  • Core dumped when I try to access MAST using latest AL version
  • Software (Plugin? AL?) allocates an enormous amount of memory (about 200GB!), then killed by system (?) if I try to use Ludovic's plugin to access JET/MAST

1.3. IMAS based Docker 

  • IMAS based Docker is designed such way it supports one DD/AL release at a time
  • At the moment, handling all UDA sources requires multiple releases of DD/AL
  • We can't provide UDA support from within container as long as we don't have one, unified, UDA implementation at client side

1.4. Catalog QT

  • Update Process (responsible for reading pulse files) should be able to read data from a variety of sources (MDSPlus files, UDA)
  • At the moment, we can't do that by implementing a single, unified approach (each UDA source requires different settings)
  • This is not a blocker as we have decoupled import process such way it can handle individual sources separately. On a long run, this is probably something we want to avoid.

1.5. Users experience

  • At the moment, using UDA requires constant changing of the environment
  • Before using given plugin, user has to unload and load whole environment from the scratch
  • It is not possible to use two, different UDA sources at the same time

2. Current configurations

2.1. WEST

  • AL: IMAS/3.28.1/AL/develop
  • plugin: Ludovic's private one

2.2. JET

  • AL: IMAS/3.28.1/AL/develop
  • plugin: Stephen's private one

2.3. MAST:

  • AL: IMAS/3.25.0/AL/4.4.0
  •  plugin: a common one uda/2.2.5 

3. Things to be done

3.1. Integration of plug-ins

We need a single version AL+plugin that handles all machines. Could you kindly integrate your codes, check it against ALL machines and provide single, working installation?

3.2. Redesign of setting plugins 

A way of setting-up plugin should be redesign. Now (different!) system variables should be set to make it working. It prevents reading from different machines within one process (!)  IMHO UDA Backend based on a machine name should point to a correct plugin, without using system variables.

  • No labels