Present/Contributing: Graeme Stewart, Claire Antel, Pere Mato, Luke Kreczko, Sapta Battacharya, Tommaso Lari, Krzysztof Genser
Apologies/Contributing: Eduardo Rodrigues, Paul Laycock, Michel Villanueva, Alexander Moreno
Journal submission: EPJC is waiting our submission but not done yet due to lack of time…
We have one reference to update, #101 (ATLAS paper, now published).
Workshop came off well! HSF overview presentations:
We had HSF sessions on Common software and Software Projects, Sustainable Software and Training. As well as plenaries on AI/ML and heterogeneous computing; and Analysis at scale and analysis challenges.
Outcomes:
Eduardo has started to prepare the inputs for the next LHCC referees meeting on 3 June.
Comments and suggestions by tomorrow, 23 May, please.
Reminder that Caterina Doglioni is now the HSF representative at IRIS-HEP.
Draft slides from the HSF for the next meeting on 3 June - comments welcome.
Planned seminars:
Venice workshop report tentatively scheduled for September. dCache project have signalled interest in presenting in a future Seminar.
HSF seminar conveners are reachable at hsf-seminar-conveners@googlegroups.com
Next SG meeting will be 3 June, https://indico.cern.ch/event/1550243/.
ACTS: Graeme will present a HSF Project Affiliation in their next dev meeting (even if exact iteration on badges not yet decided).
Future events:
Topic of generators in the neutrino community would be interesting.
Website still needs updated with current convener names.
PyHEP.dev 2025 Workshop will be held at University of Washington from July 14 to 17.
JuliaHEP 2025 Workshop will be held at Princeton from July 28 to 31.
Graeme discussed with ATLAS who are concerned about the number of different places where physical constants get defined in HEP, viz. at least in CLHEP, ROOT and Geant4.
This mainly seems to affect C++, Python is more conststent with hepunits and Julia has PhysicalConstants.jl.
Defining constants in larger HEP packages binds the physical constants to other software updates, which is not great. None of the packages, except for Julia, offer explicit versioning of the constants (and they do change, e.g., Plack’s constant was updated in 2019 and is now defined, not measured).
Q. Is there interest in having a common stand-alone library for this? C++ seems to have the greatest need. The Python package might usefully get versioning. For Julia one could imagine at least a cross-check and validation.
Generators are also rather messy here, with their own definitions of measurements, or user defined values for, e.g., particle masses, at the top of data cards.
General feeling this is a good topic to address. Graeme will organise a follow-up meeting.
The next coordination meeting will be 5 June, https://indico.cern.ch/event/1477079/.
Please sign up for chairing a future coordination meeting. (There is even a HOWTO guide).