WG 2 – Detection system performance

Thanks a lot to all of you who participated in the lively discussion about our “Detection system behaviour measurements” collection. We discussed several aspects of the table structure for our measurements and analysis data wich needs to be updated. One major discussion was again about the unique identifier. A solution needs to be found in general for Quarep. Until then we use an intermediate solution with unique identifiers in our excel sheet. Also need to ask the HTS community for their expertise. Furthermore, Kees reported from his last test runs with the APE quantiflash. His presentation can also be found here on our cloud folder. The other test places will report about their experiences and results in our meeting in February.

We did start our meeting welcoming a new member and refresh a few organisational matters. This was followed by the report from the WG9 & cochair meeting on Oct 6th: – More active members are needed for WG9. – Furthermore, an internal review process was discussed. Please revise and comment on the proposal for the “Internal Review Pipeline”. The joined group WG2and WG7 is working to consolidate the camera part of the model. The glossary still needs to be finished. A new organisation of model revision was discussed as well as potential next topics: light sources (maybe two parts: lasers, wide-field illumination), filters, objectives. We then focused the discussion on AirTable organisation and reporting of measurement and parameters from acquisition and analysis. As a result of the discussion we agreed to start from excel file in order to define the most important parameter before to transfer all of them in AirTable. Care should be taken in naming and saving the data in the correct way so that the analysis group can focus on the output parameters and their interpretation. Acquisition parameters and issue still need to be fixed and all comments should be added to the protocol draft in protocols.io once it is finalised there. (A QUAREP-LiMi-wide training on ptrotocols.io was planned for beginning of November.) Still work to do in: testing new samples (marker pen), acquire new images from chroma slide, collect and compare analysis measurements, finalise the transfer of our protocols after the training.

The camera metadata (WG2 + 7) group needs to work on a glossary, explaining the terminology used. It was decided that people from the camera subgroup will start working on this glossary. Furthermore, it was decided that we need to start thinking about the next microscope parts, for which the metadata structure and vocabulary can be standardized. Kees reported further on testing of the Quantiflash standardized light source. A continuous (DC) mode should be implemented in addition to the pulsed mode. The standardized light source will be discussed in detail during the November meeting. Personal learning sessions for Protocols.io will be offered to interested members of WG2.

At the beginning of our 18th meeting, we talked about a few organisational matters and shared general QUAREP-LiMi news: the next general assembly will take place May 25th 2022, 4-6PM CEST. This was followed by reports from the the last two WG2 & WG7 camera glossary meetings. The main topic for both meetings was what defines a colour camera. It was reported that that joined discussion group also needs input from WG2 about what we require the model to deliver. The ensuing discussion pointed out: commonly used glossary and definitions, to be used in methods sections, for spec sheets, TIER level needed with minimal specs required and additional specs available upon request. The APE Quantiflash test samples will be shipped to their first testes soon. The transfer of our data collection to Airtable is under way. More infos to both topics will come in the next meeting. Last but not least, we discussed the next steps towards finalising the first part of our protocols and moving them to protocol.io following the example and experience of WG1. Until the next meeting, each subgroup will look at their respective protocol draft, go over the text and identify open questions. We agreed to finalise the structure with a general introduction and branching or similar feature for the AD and PD protocols. The aim is to have a teaser ready for ELMI, publish the protocol in autumn. To be able to do so, we need to have more people test the protocols, measurement and analysis.