Go to the Indico Home Page Oldest event Older event Up to category Newer event Newest event Printable version
  • Compact style
  • Indico style
  • Indico style - inline minutes
  • Indico style - numbered
  • Indico style - numbered + minutes
  • Indico Weeks View
    • Switch to the management area of this event
    Login

    JCOP FWWG 29 May 2018: NextGen Alarm Screen

    → Europe/Zurich
    42/3-002 (CERN)

    42/3-002

    CERN

    24
    Show room on map
    Hide

    JCOP FWWG Meeting, 29 May 2018

    Present: Frank (CMS). Riku (BE-ICS-FD), Jonas (BE-ICS-FD), Valeri (NA62), Stefan (ATLAS), Geraldine (BE-ICS-FD), Peter B (ALICE), Peter C (ALICE), Jean-Charles (BE-ICS-AP), Cristina (CMS), Fernado (BE-ICS-FD), Clara (LHCb), Louis (LHCb)

    Indico link to event: https://indico.cern.ch/event/727936/

    Notes:

    • News about WinCC OA and JCOP Fw : see presentation
    • Updated WinCCOA Downloads page presented by Riku: approved; decision about a version/patch becoming "unsupported" will be based on approval of JCOP-CB
      • it was explained that the "unsupported" versions will be unlisted from CMF (ie the public "NICE", not the package) so that to keep the list of visible patches at reasonable length
    • Proposal to gather information about version/patch deployed in production: approved; Riku will be contacting Controls Coordination ~1/month and maintain the (new) page
      • acknowledged that the information included there will be purely informative, with no obligation or guarantee of homogenity; still the fact of having a version/patch in deployed in production and running without major faults contributes to validation and could be useful for others.
    • Decision on deprecation of fwBarGraph as of JCOP Framework-8.2.0: approved.

     

    Rafal presented the project for NextGeneration Alarm Screen => see presentation attached to Indico event

    • Clara raised a point of being able to customize the alarm screen, eg. to add a button to the alarm screen, or a right-click action (ie. "Send to logbook"); this is certainly envisaged yet already at  this stage would be good to inform Rafal about concrete requirements, or custom extensions that are currently  in use.
    • Clara would like to be able to collapse all unnecessary objects and see only the table of alarms; already envisaged (should work well especially when layout management is used); in addition  all elements are reusable in custom panels
    • Clara: Filter Hierarchies would make a lot of sense in history mode (because in live mode alarm screen is usually empty).
    • Frank/Clara: for external alarm sources it would make sense to treat them as WinCC OA alarms, so that they are archived; in particular useful if you close the alarm screen and reopen it...; it is an additional use case, not to be confused with cases such as event replay or "live" LASER display...
    • Stefan/Clara/Valeri : Event screen in "live" mode; it could act as a "log", and particularly useful if you could inject "log messages" (events?) from external sources (eg logs from event filter farms);
    • Fernando: what tests are going to be performed? We want to proove that filtering on client side is viable in large systems (more than 100 projects)
    • Clara proposed that it could then be tried in LHCb, provided local filtering is really working without impacting systems
    • Stefan: connecting to alarms of all systems in every single panel may be costly (people may want to embed it in every panel); one should test the scalability with respect to number of open UI.
    • One should think about architecture where a single manager collects alarms and publish them to an "alarm server", from which everybody would query, using some protocol. General agreement that this architecture should be considered already now, rather than postponing.
    • J-C: This may be orthogonal to architecture of UNICOS applications where one app is one system...
    • Stefan: ATLAS has a strong requirements for masking; should be properly planned, to take into account switching views, etc. Acked by others: everyone has it in some way, but not in a common way. Having lists of masked alarms, etc... Depends where we put the attribute of the alarm being masked (in the alarm config?)

     

    AOB

    • Clara: OPC-UA Server for CAEN? Is it supported for development projects? On Linux OK (not yet for production). What is pending is the address-conversion panel, which is coming.  It is planned for Framewoek 8.2.0.
    • We need to provide OPC-UA Server downloads

    Action list:

    • publish the document with requirements to get feedback
    • feedback on the document: until 30 June
    There are minutes attached to this event. Show them.