Discussion of Python in High Energy Physics https://hepsoftwarefoundation.org/activities/pyhep.html
(Sorry for the cross-post; but I can't be sure how much overlap there is between Scikit-HEP and PyHEP.)
From HSF-GSoC:
Less than a week until the deadline for submitting GSoC project ideas !
We are sending this gentle reminder targeting people who are planning to submit a proposal for this year's GSoC, but who did not make yet a pull request in the HSF repository. The deadline is next Tuesday, Feb 4 as announced already few times. We have less than 10 proposals so far, only 5 published and the rest being reviewed; last year we had 54 proposals! Please do not let this submission for the last minute since there is also a review process.
For convenience, here are the instructions (https://hepsoftwarefoundation.org/gsoc/guideline.html) for submitting a proposal. In case you have problems doing this yourself, do not hesitate to send the proposal content (following the format from the guideline) by e-mail to the admin team.
Now, I find the abstract very ambitious when I read "The talk starts with a look at what computing has looked like in the field of High Energy Physics in the past and how a lot of physicists have played major roles in the development of Computer Science. It then explores the emergence of Python as the language of choice for several physicists and two of the major libraries that have been vital to the adoption of Python in the High Energy Physics community - cppyy and uproot.". The first sentence, in particular, reflects a gigantic scope and I wonder how you're going to approach that? Its experiment software stacks for reconstruction and analysis, trigger software, distributed computing, frameworks, analysis software, simulation; you name it. I would find it far more realistic to focus solely on analysis, and that is already a big thing itself, actually. So, bottom line, I'm worried that you end you providing a very biased and potentially misleading message. Apologies if I seem negative.
Can you clarify?
PyHEP 2020 Workshop, July 11-13 2020, Austin (Texas), USA
Dear colleague,
We are pleased to announce the third PyHEP workshop organised by the HEP Software Foundation (HSF). The PyHEP, "Python in HEP", workshops aim to provide an environment to discuss and promote the usage of Python in the HEP community at large.
PyHEP 2020 will be held in Austin (Texas), USA, on 11-13 July 2020. The workshop will take place in the same city as the SciPy 2020 conference ((https:/www.scipy2020.scipy.org/) on scientific computing in Python, and will slightly overlap in time with it, to facilitate inter-community exchanges. We encourage HEP participation in SciPy.
The workshop will be a forum for the participants and the community at large to discuss developments of Python packages and tools, exchange experiences, and inform the future evolution of community activities. There will be ample time for discussion.
The agenda will be made available on the workshop indico page (https://indico.cern.ch/e/PyHEP2020/) in due time. It is also linked from the PyHEP WG homepage (http://hepsoftwarefoundation.org/activities/pyhep.html).
We encourage community members to propose presentations on any topic (email: pyhep2020-organisation@cern.ch). We are particularly interested in participation that diversifies the backgrounds of attendees - non-LHC communities, neutrino experiments, etc.
Registration will open in Spring and we will provide detailed travel and accommodation information at that time. There will be no workshop fees, thanks to our sponsors.
Some partial travel support based on need is available for some USA/UK participants, in particular for students and postdocs. We thank IRIS-HEP, the University of Liverpool and the UK Software Sustainability Institute (SSI) for this. Details on how to apply for these will be provided once registration opens.
Media information:
- You are encouraged to register to the PyHEP WG Gitter channel and/or to the HSF forum to receive further information concerning the organisation of the workshop.
- Workshop updates and information will also be shared on the workshop Twitter in addition to email. Follow the workshop @PyHEPConf (https://twitter.com/PyHEPConf) and #PyHEP2020 (https://twitter.com/search?q=%23PyHEP2020&src=hashtag_click).
Looking forward to your participation!
Organising Committee
Eduardo Rodrigues - University of Liverpool (Chair)
Ben Krikler - University of Bristol (Co-chair)
Jim Pivarski - Princeton University (Co-chair)
Chris Tunnell - Rice University
Matthew Feickert - University of Illinois at Urbana-Champaign
Peter Onyisi - The University of Texas at Austin
@Ojaswy Are you asking about PyCon or PyHEP? The PyCon abstract-submission must be closed because acceptances had already been announced (like @reikdas's).
As for PyHEP 2020 in July, we haven't said much publicly yet because we're still figuring out the new format, but it will be held as an online workshop. (That much, at least, has been established. How we're going to have online interactions with the same quality as face-to-face interactions is a problem we're still working on.)
About having the "history of Python in HEP" slide after the slide on Awkward Array, I wanted to talk about Awkward Array from the perspective of solving the computing challenges I mention in earlier slides - I mention Awkward Array again on the slide about Pybind11. Do you have any suggestions about where I can put the history of python slide instead?