JCOP FWWG 20 Apr 2021

→ Europe/Zurich

JCOP Framework Working Group Meeting

20 April 2021

INDICO Link: https://indico.cern.ch/event/1023701/

Participants: P.Golonka, M.Bengulescu,M.Suder, A.Hennessey, C.Gaspar, C.Pires, F.Glege, G.Thomas, G.Lehmann, I. Atanasov, J-C. Tournier, J.Arroyo-Garcia, J.M.P. Rodriguez, L.Sargsyan, L.G.Carioso, M.Vazquez Muniz, M. Lechman, P.G.Verdini, S.Schlenker, W.Karimeh

News on WinCC OA and Framework:

  • Less and less likely that we would upgrade to WinCC OA 3.18 before the end of LS2
  • New version of fwFSM with numerous bugfixes is now available on the downloads page
  • If necessary, a complete release of the Framework may be arranged for

Presentation of Marc & Mariusz, followed by the demonstration of the new trending in action.

After the demo the following points have been raised

  • PGV: with a single push a button and have vertical axis for all the trends the same. Very often plots are homogeneous, even though units are not set. This would be useful on RUNTIME not configuration time
  • PGV: what will be the impact - how much work would need to be foreseen for conversion of existing projects to the new trending - addressed in the remaininig part of presentation.

In the final part of the presentation Marc presented the plan and a list of open questions related to compatibility, asking for feedback.

  • Asked Clara for assistance in porting the lbTrending functionality
  • "Rolling releases" for deployment on the ATLAS test infrastructure; this rolling release would be available for anyone interested in "alpha-testing" and exploring corner cases
  • LHCb: it may be useful to read the new data model, but we'd rather just go ahead with the migration, as it is done e.g. for OPC-UA. If the new component works well, it should be just fine for one-way conversion of all data etc. ATLAS supporting the idea in general: global migration should be fine. Also for CMS it would be fine. ALICE is going to debrief internally and will let us know.
  • ATLAS: at some moment a release will need to be done, and the new phase will start with feedback, bugfixing, etc. It would be useful to have this delivered as a new component (with "either-or") not to mix things.
  • We do not want to force people to eg. upgrade to the newest version of the whole framework to test things - ideally the dependencies should be well isolated. We should not couple fwTrending with many other changes in the framework - encapsulate the cross-component dependencies. Maybe it should be delivered as an "out of band" release, not synchronized with framework. Not sure what would be possible.
  • There must to be a transition period. The problematic part is the roll-back scenario. How critical is this to have it well developed?
  • In 3.18 there is the strict-addressing mode for ref panels, preventing the manipulation of objects inside it. Hence it should probably be assumed that this won't be possible (or would require extra "exposure" of properties that need to be manipulated
  • Possible additional feedback to be followed-up at the AOB point of the JCOP FWWG in 2 weeks.

Next FWWG: proposed on 4th of May.

There are minutes attached to this event. Show them.
    • 14:00 → 14:10
      News on WinCC OA and JCOP Framework 10m
      Speaker: Piotr Golonka (CERN)
    • 15:00 → 15:30
      AOB 30m