Meeting Notes
Software Documents
How should we read the documents? Only focusing on heterogeneous computing?
- Read the documents with respect of the document's parameters
- Our mandate should cover all software, of which heterogeneous is only a part; and we are also concerned with soft matters - training and career paths
There is an IN2P3 document, produced by a new WG, with a lot of material regarding open software, data and tools, with directions for the RA
- Bruno is on this WG and has helped to prepare it
- Should become public, but it's not yet
- Can provide an early summary?
About 1 month to read and summarise documents
- By end of May
Survey
- Add link for FAIR Software Principles
- ARM as an alternative CPU architecture
- Ask about principle dependencies they have for their software ecosystem
- e.g., ROOT, CORSIKA, Geant4, ML libraries, ...
- How does software interoperate with other parts of the ecosystem
- Format
- Some will be yes/no (good for easy analysis)
- Some will have to be guided free text (harder to analyse)
- Should we work with contact points, or make the survey general?
- Contact points are good to ensure an 'expert' view, but might reduce diversity of responses
- Software efforts are always needed, but they compete against other demands
- How does software integrate into the lifecycle of the experiment (planned, written, sustained, preserved, ...)
- Larger experiment/collaboration policies play a big part in some aspects
Timeline
- Want survey out before summer
- Will require coordination with other WGs
Links