Present/Contributors: Dario Menasce, Giulio Eulisse, Graeme Stewart, Benedikt Hegner, Ian Bird, Simone Campana, Pere Mato, Thomas Kuhr, Mike Sokoloff, Liz Sexton-Kennedy, Eduardo Rodrigues, Stewart Martin-Haugh, Pete Elmer
News, general matters
General Matters and Roadmap
Publication strategy for Individual WG Papers
- We noted that conversion from Google Doc to LaTeX was far less
painful than had been thought so our recommendation for arXiv
publication for individual papers is updated. This was
followed to get the Software Development paper to arXiv late
- We have to decide what to do when the WG paper is in a much less
developed state than the roadmap (Generators, ML) or only only
really exists in the roadmap (Security).
- Need to revisit the detailed paper ensure consistency. Then
will follow the procedure.
Software Trigger and Event Reconstruction
- Neither Vava nor David can attend today. Apologies. We plan
to pick up improvements to our text made during the final
editing of the cwp and hope to submit to the archive next
week. We already have completed one pass of gathering
authors and will do another.
Data Organisation, Management and Access
Data and Software Preservation
Data Analysis and Interpretation
- Ric (unable to attend today) will do final paper edits next
week, ready for last circulation before arXiv.
Event/Data Processing Frameworks
- Liz at CERN next week, will follow up with Benedikt.
Careers, Staffing and Training
- Dario will backport material from the roadmap.
Facilities and Distributed Computing
- Clean up needed of the WG document.
- Needs some work from roadmap document. Should get CMS,
Durham IPPP inputs as well.
- John Harvey - what’s the plan for producing a document for the LHCC?
Ian - will give the LHCC a strategy document in February; the WLCG
view of the CWP Roadmap.
- Summary yesterday in GDB meeting.
- All local organisation points are done.
- Registration has quietly opened yesterday.
- Need to chase up conveners (we have a wish list - need to
- Goal is to follow up on the CWP roadmap, identify and work on
- Plenty of parallel session opportunities - working groups should actively propose
- Discussion: Mike - goal should be cross-experiment development
collaborations. Useful to have ‘outcomes’ in advance and try to
structure the workshop towards them; though sometimes the outcomes were
different to those originally envisaged. E.g., in software
development could try to discuss tools and methods to implement
suggestions in the white paper. Giulio - could discuss an
incubation procedure to help people to get started on their
projects. Simone - should focus on priorities for WLCG.
- Please check the agenda.
Main point is to get the right people there.
- Reminder: 1st “Python in HEP” workshop to be held as a pre-CHEP
event on 7-8 July 2018, so just before CHEP 2018 itself.
- Goal of workshop(s): provide an environment to discuss and
promote the usage of Python in the HEP community at large.
- Organisation progressing well and we now have a reasonable idea of
workshop structure & agenda.
- Organising committee: Eduardo, Graeme, Jeff.
- The 1.5-day agenda will be composed of plenary sessions dedicated to
the following topics:
- Historical perspective and overview
- PyROOT and Python bindings
- HEP python software ecosystem
- Distribution and installation
- Analysis frameworks
- Python 2 versus 3
- Open discussion on education and training
- There won’t be any training sessions or hackathons in this first
workshop, but some level of tuition will come in small bites in
the various presentations, which will try and be educative, not
just informative, with well-defined examples relevant to the
topics under discussion
- One of the goals of this PyHEP workshop will be to identify
training workshops or hackathons the community would like to
have in the future
- Announcement will go out on Monday 15th
- Dedicated page + advert on HSF website
- Announcement email to be sent around
- Once the announcement is out, find speakers for presentations
foreseen, finalise the agenda, ...
- Graeme still chasing HepMC status.
- HSF New Year Newsletter
- Should cover CWP status and upcoming workshops
- Make sure we propose a CWP talk for CHEP itself.