Task 3. Strategy for communication between biobanks, including a common nomenclature, compatible software techniques and appropriate information transmission polices
Task 3. 10: Promoting HiPEAC Start-Ups
Task 3. 1: Conference 4
Task 3. 1: Scientific coordination Progress towards objectives and significant results
Task 3. 2 Implement the code for under 3.1 defined specifications and integrating the results achieved in tasks 2.2 and 2.
Task 3. 2: Summer School 16
Task 3. 3 Perform experiments with the system as implemented in task 3.2. Task 3.4 Report on the experiments performed. D3.1 (Month 21) Implementation of language evolution and communication functions (code + documentation) D3.2 (Month 36) Research report on the evolution of language, communication and cooperation. M3.1 (Month 11) Agreement on the set-up required for evolving language, learning how to use communication and how to react properly on linguistic communication, summarised in interim report. M3.2 (Month 26) Point at which the language evolution part is integrated in the entire project, so that the real experiments can start.
Task 3. 3: HiPEAC Journal Accepted papers
Task 3. 4: EDM toolkit and framework extensions Progress towards objectives and significant results
1. The multithreaded Gaudi framework is currently unable to safely process multiple events that correspond to different distinct detector states.
2. The condition database software that is used by the ATLAS and LHCb experiments is largely unmaintained and possesses major conceptual flaws. Its replacement, which is currently being implemented, will need to be integrated into Gaudi. After iterating with experiment and framework stakeholders, several implementation alternatives were proposed and are currently under evaluation, aiming at a condition handling solution that is suitable for all Gaudi-based experiments thereby reducing the need for experiment-specific code. Although the focus has been on Gaudi-based experiments so far, it is planned to explore the possibility of integrating this infrastructure into other HEP frameworks in the longer term. In the Y1 reporting period, task 3.4 had no milestones and no deliverables to submit.
Task 3. 4: HiPEAC Roadmap
