...
- 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
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
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.
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
Current configurations
WEST
- AL:
IMAS/3.28.1/AL/develop
- plugin: Ludovic's private one
JET
- AL:
IMAS/3.28.1/AL/develop
- plugin: Stephen's private one
MAST:
- AL:
IMAS/3.25.0/AL/4.4.0
- plugin: a common one
uda/2.2.5
Things to be done
Integration of plug-ins
...