LGCReport - Work Update Status

Europe/Zurich
926/1-039 - Priority BE-GM (CERN)

926/1-039 - Priority BE-GM

CERN

12
Show room on map
Description

Short update on the development status and future of LGCReport

Participant: Alban VIEILLE, Camille VENDEUVRE, Dominik WASSMER, Guillaume KAUTZMANN, Pascal SAINVITU, Pierre VALENTIN, Simon HUANG, Vincent BARBARROUX

Presentation by Dominik WASSMER: LGCReport Gathering Feedback and Work status update

  • As time performance was one of the critical issue for the issues, the developer team investigated and presented its results (see slides).
  • Functional Specifications: It can still be completed in the future, especially once development is picked up more intensively.
  • Future steps: priorities on SurveyPad Qt Migration and PyRabot development

 

Discussions:

Time performance:

  • The users could also get the test files and try on their PCs to gather more data.
  • Having representative files could also be useful.
  • Being able to reduce the time performance from 10 to 4-5 seconds is not enough. To be usable, the loading time should take less than 1 second.
  • Collecting time performance data -for example adding the loading time to a log- is not straightforward in the project, no solution is yet available.

 

LGC2Report versions

  • v1.1.0: no issues was noticed yet. It is still not really used. The res file is still more convenient to use.
  • v1.2.0_beta: The users managed to use the template file (LGC_Report.html) of the version but when trying to save the current configuration of the hidden configurations, it did not work properly. (The issue was fixed after the meeting)

 

Priorities:

  • The users agree that it is more important to focus on SurveyPad and PyRabot, so that more bugs are fixed. There are still many issues to be fixed on LGCReport, so it needs a lot of development. The development could be done during/after the YETS for example.
  • Nevertheless, LGCReport aims to become the main output for the long term, as LGC improvements in the writers will be minimal - i.e. no big quality of life / new features, large refactor (ex: Frame presentation) ...

 

After/During the YETS 2024:

  • ACTION: All, continue the work on the specifications Link
  • ACTION: Continue the development on LGCReport (time performance, adding features to speed the users workflow...)
There are minutes attached to this event. Show them.
    • 14:00 14:30
      Presentation - Dominik Wassmer: Presentation on LGCReport development
      Convener: Dominik Wassmer (Cern (GRAE))
    • 14:30 15:00
      Feedback - Conversation Session 30m