... | ... | @@ -36,6 +36,55 @@ Pending actions as of 02/10/2020: |
|
|
* Action 34 no longer relevant after December BSC, Action 37 completed in December 2020 BSC
|
|
|
|
|
|
|
|
|
Summary of the meeting (20/01/2021)
|
|
|
-----------------------------------
|
|
|
|
|
|
**Attendees** : Jordi Bodera, Jean-Claude Biasci, Andy Gotz, Jens Meyer, Matias Guijarro, Veijo Honkimaki, Harald Reichert and Armando Solé
|
|
|
|
|
|
|
|
|
**1. BLISS and BCU priorities for 2021**
|
|
|
|
|
|
Jean-Claude explained that information about the evaluation of projects is available: https://confluence.esrf.fr/display/PPCKB/Results+of+the+Project+Request+Campaign
|
|
|
|
|
|
Some issues are identified, like overlap between tomo-bridge and BM18 and also ID17.
|
|
|
|
|
|
The priorities for the BLISS team should be
|
|
|
|
|
|
* 1st: ensuring that the 13 beamlines using BLISS are fully operational
|
|
|
* 2nd: carry on supporting beamlines with their operational needs
|
|
|
* 3rd: EIGER2 integrations
|
|
|
* 4th: supporting new EBSL projects
|
|
|
* 5th: any other request
|
|
|
|
|
|
Harald explained that a Gate A letter for ID17 has been issued and that Council supports spending 1M€ for that project. Harald also explained that there is plenty of interest from other research infrastructures to work with the ESRF in software-related projects to fully exploit the capabilities of BM18 with significant amounts of money is expected to be granted to the ESRF (or in-kind contributions with staff). Jordi added that for this we should formalise a project structure and specify the scope and requirements to successfully deliver such project.
|
|
|
|
|
|
**2. Pending Actions**
|
|
|
|
|
|
.28 Confirm Bliss conversion plan & SPEC support end: Jens shared a slide with the information. **THE LINK WILL BE ADDED AS SOON AS POSSIBLE**
|
|
|
|
|
|
.33 BLISS Steering Committee future: It was agreed that changing the structure of the BSC is a good idea. The objective of having representatives that are close to the requirements of the software and technical solutions was endorsed. It was decided that by the next Bliss Steering Committee, the new representatives for the meeting would have been selected and the current structure could be formally shut down to let the new structure take its place.
|
|
|
|
|
|
.36 Improve backwards compatibility & integration testing: Matias reported no progress. Andy highlighted that it is important that any new version is stable and its life time (until a new version is available) is such that it is worth moving for BLs. At the moment some beamlines are concerned that there are too many changes too often that introduce too many issues/bugs.
|
|
|
|
|
|
.38 Energy Scans project leader and plan: Jean-Claude confirmed that Jean-Michel Chaize is the leader for this work, with Nicolas Leclercq planning to take over once Jean-Michel retires. It was noted that the project cannot advance as quickly as desired due to lack of available manpower in ASD.
|
|
|
|
|
|
**3. Status update on Beamline conversion to BLISS from SPEC**
|
|
|
|
|
|
Jens already covered this topic within issue .28
|
|
|
|
|
|
**4. Status update on BLISS Core development and GUI**
|
|
|
|
|
|
Matias presented this slides: **LINK TO PRESENTATION STILL MISSING** and explained that there are 3 categories of issues with the current BLISS version:
|
|
|
1. excessive CPU usage
|
|
|
2. Overhead time
|
|
|
3. Timeouts
|
|
|
|
|
|
Matias also explained that there is a planned feedback meeting for 23/02/2021 so scientist can use the new version of BLISS (1.7 was released 4th January) and provide some feedback. Until then, the priorities would be fixing bugs and then add new features.
|
|
|
|
|
|
A brief discussion followed on the topic of new features/bug fixes changing the core of BLISS and introducing issues to BLs that have stable behavior, thus creating new issues. While it is possible to ensure versioning of existing methods to do not break working features Matias explained that as it is early in the lifecycle of BLISS rather than creating complexity with several versions of the same feature it should all be fixed in the core.
|
|
|
|
|
|
Matias also presented some strategy issues to be decided and sorted, which the new BLISS Steering Committee structure will need to work with.
|
|
|
|
|
|
Minutes from previous meetings:
|
|
|
* [18th BSC 04/12/2020](https://gitlab.esrf.fr/bliss/bliss/-/wikis/18th-BLISS-Steering-Committee)
|
|
|
* [17th BSC 28/10/2020](https://gitlab.esrf.fr/bliss/bliss/-/wikis/17th-BLISS-Steering-Committee-end-October)
|
... | ... | |