Present: Hampus, James (BI-BL), Steen, Stephane, Stephen (BI-SW)
Operational requirements
- Working point for instrument hardware development:
- Integrated profile @ 1kHz .
- Bunch-by-bunch measurement every 10ms over the entire PS cycle.
- Needs to be updated in light of experience with the prototype instrument in 2017 and consideration of what is practical to store / useful to make available on the operational software side.
Current software status
- Instrument software is split in two independent parts corresponding to the two hardware systems: 1) Slow control & monitoring and 2) Pixel detector control and readout.
- Slow control & monitoring:
- FESA classes have been developed to provide an interface to the the Siemenes PLC that controls all power supplies (BGIPower); the cooling system (BGICooling) and to monitor temperatures (BGITempr). Expert GUI under development by BI-SW.
- FESA navigator currently used for all slow control and monitoring.
- Pixel detector control & readout:
- Monolithic "Panda" expert application written by Hampus in C++/Qt.
Software objectives for 2018 run
- Slow control & monitoring:
- Expert GUI to be completed by BI-SW for start of 2018 run.
- Pixel detector control & readout:
- Hampus will implement sofware architecture based on the gRPC server / client concept (slide #6). However, gRPC is not compatiable with long term maintanence by BI-SW, therefore, this will be an interim development that will need to be replaced in the long term (see blow). Nevertheless, BI-SW agree to develop a "BGIUser" FESA class - which will be a gRPC client - which will allow OP to use the system in 2018 and will provide valuable experience for subsequent development.
- BGIUser FESA class functionality to include:
- Acquisition settings (gate length, integration length, cycle repetitions),
- Start/stop acquisition,
- Get profile data.
- Hampus will provide BI-SW with a test server - which emulates the pixel detector - for the development of the BGIUser FESA class.
Software objectives for 2019 - ...
- Gradually move all software related matters to BI-SW.
- Interface between the “software" and "hardware" to be defined, but needs to be something that is suitable for long term maintaince by BI-SW (sofware-side) and BI-BL (hardware-side).
- Timeline: operational software to be ready for prime time at the start of Run 3.
Next meeting: Propose to have another meeting in November (date/time tbd.)