GCS software development

Europe/Zurich

18/03/2020

 

-Alarms (Mara's report)

Doct Stds phone is now receiving alarms and warnings.

Mara will report during weekly meeting

To experiment technical responsible and piquet to fille the info for sms not received

Link: https://espace.cern.ch/gas-control/_layouts/15/start.aspx#/Shared%20Documents/Forms/AllItems.aspx?RootFolder=%2Fgas%2Dcontrol%2FShared%20Documents%2FActivities%2FSmsMail%20notification&FolderCTID=0x012000852472212F969B4E9850475116730F2C

 

A short collection of examples:

 

CMS:

-Why PGS is half grren. Is it due to air?

-DT analysis is half green due to normal cycle --> DT top module is half green --> no good representation

-Humidifier DT forced off. Why? Is it because it would need a stop/start of the system to consider recipes change? Can we think to a solution to that?

-Propagation of alarms to main pco requires creation of new alarms. True?

-Alarm during maintenance: Michal to propose a solution to not stop interlocks but only notifications

 

ALICE:

ALIHMP_Di_61InPresAI --> Michal to clarify

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.

 

NA62:

Straw: Backup alarms alarms added on PT6x79 and 6x75. To add also text.

Added after meeting: RICH: do we have alarm active and sms on PT6125

 

Non-LHC alarms on piquet phone

 

Overview page with main parameters for each gas system to be proposed. Something like exhaust++

 

What is TIP? Michal to prepare a presentation for next meeting

 

Web page for main parameters to be developed by Gianluca. Now possible because all data are on GPN/DIP

 

Plots issues (some):

-auto-range

-problem saving plot config for some users (is it now solved?)

-changes are lost when zoom

-in zoomed view for "dynamic trend" if I add something I have to close and open again

 

Recipes not active info/warning.

As discussed in the past, something to prevent start-up of a system if recipes are not active

 

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 --> Gianluca, Michal --> to be discussed with Geraldine

 

Profibus and CANbus monitoring tools --> Gianluca, Michal (+ Marc?)

 

Find a way to have good 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?...

There are minutes attached to this event. Show them.