During startup we should take some time one of the LLRF/RF experts and have a look at which alarms still pop up that do not make sense
LLRF will implement a system to switch off alarms coming from a given station or from stations in a given state.
We decided that it would make sense to make a more advanced RF Station panel that takes relevant information out of the RF expert panel and is tailored to our operational needs, this specifically includes additional information about what is going on during an RF failure, if the resets work, what actually caused the failure, that allows us to reset the trig/race detection and so on -> We should figure out who will make this panel
Meeting about communication between photonics & the control room:
Nicole started to work on a panel that summarizes the machine status for the photonics guys and on their side they are working on a synoptical panel for their devices, we will then have to see which of them are relevant for us when we tune the FEL and make an overview panel for us
we should introduce a "proper" string status PV for communication with the experimental station like it is done for the SLS -> Andreas Lüdeke has set it up for the SLS and can aid us there
there should also be a channel-based communication between control room and beam line (attended, unattended, offline like at SLS or maybe slightly differently)
An intercom system similar to Proscan would be useful.
Photonics will prepare a synoptic overview of the photon lines. This will be maintained by them.
A generic solution for acoustic alarms would be useful. For the moment this is restricted to alarm handler alarms and tendis.
BLM/LLM application: Marco and Christoph have prepared a specifications for the application. They should now contact Simon Ebner to get support/advice on how to best structure the code. Whenever possible we should stick totools supported by controls.
Following the DRPS upgrade the MPS channels will be adpated with a longer time constant. One should check if this is still convenient for beam tuning. In case the signal is too slow we should use alternative channels (check what is already available). A collection of stripchart req files with groups of BPMs would be useful.
Synoptic viewer: Nicole is working on a first operational version of the synoptic viewer including beam obstacle display, device status and related panel. In some case the related panel may be a dedicated panel for the synoptic. Direct controls of devices from the synoptic viewer (example magnet setting) will only come later.
HLA structure: Christoph is working on a document specifying the interface between the different HLA. The main issue is about energy channels and energy independent settings for magnets to allow automatic scaling of the optics based on the energy. Initially we should rely on the channels provided by the online model. Christoph will check with Masamitsu what is already provided.
Several improvements of the snapshot tool have been requested. Christoph will follow up with Simon.
The dailly routine should be checked next week. The output saving will be improved (TEX has been installed on the consoles).
The data saving will be improved using a library provided by controls. This should standardise data format and facilitate laser profile comparison and history display. A set of channels to hold daily routine measurements should also be set-up.
A dailly routine for the injector set-up will be prepared. Brain storming meeting next week.
The tunnel access script is ready and has been approved by LLRF/Florian. The scripts were moved to the correct location /sf/op/bin and renamed (they should be independent of the original LLRF scripts) and the panel can be started from the launcher. To be tested next week.
There are minutes attached to this event.
Show them.
