by

Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    Henry Schreiner
    @henryiii
    This sounds interesting (not useful ATM, AFAICT, but interesting): https://github.com/iodide-project/pyodide/
    Henry Schreiner
    @henryiii
    And, unrelated, here’s a language popularity animation (as always, this varies a lot depending on the data used): https://twitter.com/marcusborba/status/1205819678842609664
    Pratyush Das
    @reikdas
    I actually met the main author of pyodide last month at Scipy India :D
    Henry Schreiner
    @henryiii
    And, since no one has posted it: https://pythonclock.org runs out tonight! Though, to be fair, the final release of Python 2.7 (2.7.18) actually comes out in April - tonight is just the code freeze.
    Hans Dembinski
    @HDembinski
    The animation of Marcus Borba looks cool, but since he does not reveal where the data came from, it is unciteable...
    I still enjoyed watching it. It is interesting to see how there is the age of Pascal, which fades, then comes the age of Java, etc. Now seems to be the age of Python :+1:
    C++ is also still one of the top compiled languages.
    Hans Dembinski
    @HDembinski
    The article about the Zen of Python is very good for those who do not click with the Zen of Python intuitively as I did. Most of it only starts to make sense when you gain some experience with designing software and fell into a few traps along the way. These guidelines are great. They are guidelines, not rules, but if you follow them, your software becomes much better.
    Jim Pivarski
    @jpivarski

    (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.

    Pratyush Das
    @reikdas
    Hi! I will be giving a talk titled "Python in High Energy Physics" at PyCon US in April. I have a window to make changes to my abstract and I would greatly appreciate any suggestions about what you would like to see in the talk or if you would like me to make any changes to my abstract. Here is a link to the abstract that was accepted - https://docs.google.com/document/d/1MHOPUB9KYjG1A_RQ67fyNgPoy5-jxbvcCrQQZmcQ7Ys/edit?usp=sharing
    Andrzej Novak
    @andrzejnovak
    nice
    Pratyush Das
    @reikdas
    Thanks for the suggestions @henryiii !
    Eduardo Rodrigues
    @eduardo-rodrigues
    Hi @reikdas, I've just added a few comments.
    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?
    Pratyush Das
    @reikdas
    "The talk starts with a look at what computing has looked like in the field of High Energy Physics in the past" - I was mainly going to talk about PAW and the emergence of ROOT. I guess I do mean just analysis.. (I'll update the abstract to reflect it). "and how a lot of physicists have played major roles in the development of computer science" - I was thinking of something similar to slide 9 of Jim's talk (https://github.com/jpivarski/2019-09-13-history-strangeloop).
    Eduardo Rodrigues
    @eduardo-rodrigues
    Thanks for the link. Yes, this kind of historical statements are good. But you will have to be very brief on the "general intro" ;-).
    In any case, do keep in touch with PyHEP so that the talk is "the best possible" ...
    Pratyush Das
    @reikdas
    Sure. Thanks!
    Eduardo Rodrigues
    @eduardo-rodrigues
    Just for the record, we now have 100 people subscribed to the channel :-)! Nice!
    Hans Dembinski
    @HDembinski
    :+1:
    :)
    Matthew Feickert
    @matthewfeickert
    More of interest for the PyHEP 2020 organizers, but when I was at the Lake Louise Winter Institute I met Claudio Kopper (https://pa.msu.edu/profile/kopper/) who works on IceCube and he seemed quite keen about PyHEP. So we will hopefully have someone from his group attending
    Eduardo Rodrigues
    @eduardo-rodrigues
    Thanks @matthewfeickert. It would be great to see participation from IceCube and others at the workshop.
    Eduardo Rodrigues
    @eduardo-rodrigues

    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:

    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

    Eduardo Rodrigues
    @eduardo-rodrigues
    Useless to say - please broadcast the announcement through your experiment and/or country mailing lists … Thanks a lot!
    Henry Schreiner
    @henryiii
    PEP 584 was merged into Python 3.9. This will allow dictionaries to be combined, that is, dict1 | dict2 or dict |= other_dict
    Henry Schreiner
    @henryiii
    (just like sets)
    Matthew Feickert
    @matthewfeickert
    nice
    Hans Dembinski
    @HDembinski
    Makes sense!
    Pratyush Das
    @reikdas
    PyCon USA got cancelled. They have given speakers the option to record their talks and submit it to be uploaded on PyCon's youtube channel, so I'll probably be doing that.
    Ojaswy Akella
    @Ojaswy
    Is the application for presenting at the event still open? I am intersted.
    Jim Pivarski
    @jpivarski

    @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.)

    Ojaswy Akella
    @Ojaswy
    Hello @jpivarski, I am interested in presenting at PyHEP. In @eduardo-rodrigues message above it's mentioned that community members are encouraged to propose presentations. I would like to know more details about that (any requirements for presenters and topics)
    If permitted off the top of my head, I would like to talk about HL-LHC project and how ML can help us in analysis.
    Eduardo Rodrigues
    @eduardo-rodrigues
    Hello @Ojaswy, that's right, we encourage abstract submissions as it won't be just invited talks. As @jpivarski says, we are reorganising the workshop because of covid-19. We will send another email as soon as we're set. As for details, abstracts are informal-ish, and it's done via the email provided on the PyHEP 2020 Indico agenda (not on this cht ;-)). The one requirement is that it fits the workshop scope, of course, so Python is central ...
    Ojaswy Akella
    @Ojaswy
    @eduardo-rodrigues @jpivarski How do I be a part of the mailing list to receive any updates on the program?
    Jim Pivarski
    @jpivarski
    @Ojaswy We'll be sure to announce it here.
    Eduardo Rodrigues
    @eduardo-rodrigues
    I believe anyone can subscribe to that mailing list, at least with a CERN lightweight account. If that an annoyance because you're not quite in the field then be reassured since, as Jim says, we will always announce things here too. And of course on the HEP Software Foundation general forum (see https://hepsoftwarefoundation.org/forums.html).
    Ojaswy Akella
    @Ojaswy
    Thank you for the information.
    Pratyush Das
    @reikdas
    I finished a draft of the slides for my upcoming PyCon talk - https://drive.google.com/open?id=1KKezj9a3V6-GBg8gf1Hv9NYUjF-B5yhs . I would love to hear any feedback.
    Henry Schreiner
    @henryiii
    Eduardo Rodrigues
    @eduardo-rodrigues
    Hi @reikdas, thank you for sharing your slides. There's a fair amount of interesting material in there, and the talk is a difficult one since so broad. I think you should make it really clear in the title and first pages(s) that the talk is a very biased and personal account from your own experience - a disclaimer. For a start you're not a particle physicist, after all, not have you been working in particle physics ;-).
    I did not download the slide but it seems that you do not have links for the many references that you should be having: refs (GitHub repos) to packages, refs to some talks presented e.g. at PyHEP 2019, etc.
    I do not understand why it is only in slide 12 that you talk about "history of Python in HEP" when you even talk before about awkward-array. That seems … well, awkward to me.
    On page 2 you should say that particle physics studies not only the nature of particles but also their interactions. This is crucial.
    Also say "some of the largest …". Indeed these days and in the near future some of the astronomy collaborations are/will be just as large.
    Eduardo Rodrigues
    @eduardo-rodrigues
    I'm not going to dive to more details but I hope this helps. Thank you again for advertising the field in such an important conference. I hope your talk is well received :-)! Let us know.
    Pratyush Das
    @reikdas
    Thanks for the suggestions!
    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?
    Eduardo Rodrigues
    @eduardo-rodrigues
    Oh, maybe I read to quickly. I guess this depends on how you discuss the slides. If you explain why HEP needs awkward array - well, jagged structures - then it's probably just fine what you did. Meaning, in some sense you talk about requirements and evolution, wrap up with an overview on historical developments, and then go more to ongoing activities, projects and packages. Seems fine. Again, depends on your wording. Sometimes a little sentence helps the navigation from page to page :-).