14/04/2020
Alarms (Mara's report)
ALICE 1 warning from PGS flow -> LPh, Gianluca
Examples discussed:
CMS:
-Why PGS is half green.
Michal to check, describe and write few lines of proposal (JIRA:GCSUR-111)
-DT analysis is half green due to normal cycle --> DT top module is half green --> no good representation
Ticket open -TICKET NUMBER-. Just to follow. Modif will be done once back (JIRA: GCSUR-112)
-Humidifier DT forced off.
Introduce parameters to select if module is needed or not for run.
Change should not require stop/start of the system. Can we apply the same to purif? why today stop/start is required? (JIRA Purifier:vGCSUR-110) (JIRA humidifier: GCSUR-113)
Check if for RPC we have a parameter (for humidifier or for change without stop/start? I don't remember...) - Michal: there is no parameter,global ticket for humidifier modif already created (JIRA: GCSUR-113)
-Propagation of alarms to main pco requires creation of new alarms. True?
-Remove notification for propagation of alarms from child to parent -> Michal
-Alarm during maintenance: Michal to propose a solution to not stop interlocks but only notifications
How other groups are dealing with the same problem? -> Michal
ALICE:
ALIHMP_Di_61InPresAI
ALIHMP: red = backup active --> modify to something else: full green backup active. Full red backup pressure error, empty green during run when backup is not used.
--> it will be included during TPC upgrade (test will be needed) (JIRA:ALGCS-729)
NA62:
Straw: Backup alarms alarms added on PT6x79 and 6x75. To add also text. (JIRA:GNA-94)
RICH: Implementation warning/alarms on PT6125 ongoing -> Michal (JIRA:GNA-95)
CEDAR: Implementation warning/alarms on PT6104 or PT6105 to be defined -> Roberto
Description of alarms to be studied for the future. It requires new functionalities to be developed by SCADA team. Michal to add Roberto to jira ticket and to inform about future developments. is it correct? -MICHAL TO CHECK-(JIRA: ENS-26733 / UCPC-1052)
Non-LHC alarms on piquet phone
to be evaluated. How many? Did we said to include in Mara/Gianluca phone to have statistics? I don't remember conclusion.
Overview page with main parameters for each gas system to be proposed. Something like exhaust++
checklists should be "standardized" before
--> fix dedicated meeting (next week?).
What is TIP? Michal to prepare a presentation for next meeting (JIRA:TIP-161)
Web page for main parameters to be developed by Gianluca. Now possible because all data are on GPN/DIP
Plots issues (some):
-auto-range (add details)
-problem saving plot config for some users (is it now solved?)
-changes are lost when zoom -> to be monitored (is it known/reported? -> Michal)
-in zoomed view for "dynamic trend" if I add something I have to close and open again -> to be monitored (is it known/reported? -> Michal) (JIRA: ENS-27012 )
Recipes not active info/warning.
As discussed in the past, something to prevent start-up of a system if recipes are not active
can be implemented before Run3? -> Michal to check -MICHAL TO CHECK- under discussion with Geraldine
LHC logging and winccoa archiving --> Michal, Gianluca --> to understand differences --> Gianluca can you prepare something?
Deadband/smoothing
Configure all deadband/smoothing level
Winccoa level --> ongoing for alice --> Gianluca
Plc level --> extraction ongoing (polish student is extracting data) --> ppt for next meeting
Alarm/warning levels from winccoa
Is it possible to have a kind of download table --> from recipes? -> Gianluca, Michal --> to be discussed with Geraldine
Profibus and CANbus monitoring tools --> Gianluca, Michal (+ Marc?)
Find a way to have an effective communication with BE, other users and software development:
Michal reported that Lukasz is rapresenting "our" section but we never had discussion with him. Are there dedicated meeting? How often? Can we organize meeting to give feedback to Lukasz?...