Python in Heliophysics Community (PyHC)

Promoting and facilitating the use and development of Python for Heliophysics.

A community knowledge base for performing heliophysics research in Python, aiming to provide a variety of tutorials, resources, a list of useful packages, general discussion, and advice.

Our Mission Statement

Facilitate scientific discovery by promoting the use and development of sustainable open-source Python software across the solar and space physics community; improving communication and collaboration between disciplines, developers, and users; establishing and maintaining development standards; and fostering interoperability and reproducibility.

Our Strategic Goals

  • Coordinate development across projects to minimize duplication of effort and share lessons learned
  • Promote best practices for software development, documentation, testing, and dissemination
  • Increase community awareness of and participation in projects
  • Promote scientific reproducibility and software sustainability
  • Educate and support the Python user community in solar and space physics
  • Foster an open-source Python software ecosystem for heliophysics research and education
  • Identify community needs for future development
  • Identify and pursue opportunities for financial support
  • Enable efficient interdisciplinary research


PyHC meets in person twice yearly. Telecons are held approximately every two weeks on Mondays at 09:00 AM Mountain time, but this can fluctuate depending on holidays, conferences, etc. Meetings and telecon times are available on our Google Calendar:


PyHC Spring 2023 Meeting Dates Announced

PyHC’s Spring 2023 Meeting will be the first hybrid meeting to take place since the pre-pandemic times!

We’ll host the in-person portion at LASP | CU Boulder, and online participation will be available at this Zoom link (Meeting ID: 973 7236 9069). The Zoom sessions will be recorded. It will be spread across three days, starting Tuesday, May 16th, 2023 and ending Thursday, May 18th, 2023. We’ll hold tutorial, hackathon, and project update sessions, as well as some other discussions that are relevant to the community. See the full agenda for dates/times of the various sessions. Note that the agenda is subject to change.

The meeting’s web page can be found here. Registration—which is free but required—can be found here. The meeting’s web page also has a link to registration, as well as the Zoom telecon information, links to important documents, etc. If you’d like to join our mailing list to learn more information about the meeting and other upcoming events, please see the PyHC Contact page for instructions. You’ll also find links there for joining our Element and Helionauts chat groups (where we discuss various PyHC issues/topics, as well as discussing other Python-related questions), as well as a link to connect with PyHC on Twitter!

Registration Deadline: EOD, Friday, May 12th, 2023. Note: If you already registered and later decide to change your registration, you should be able to do that directly, but if you experience any difficulties please email Julie Barnum or Shawn Polson.

New Way To Cite PyHC

You can now uniquely identify PyHC as an entity with this ROR ID:

ROR is a global, community-led registry of open persistent identifiers for research organizations. ROR IDs function much like DOIs but they are used for research organizations rather than individual research outputs. Learn more about ROR IDs on their website. Let’s spread the word about this new citation mechanism!

New Website URL!

We are excited to announce that we have purchased the domain. A very special thanks is owed to Pete Riley with Predictive Science Inc. for making the purchase and handling the renewals. At present, redirects to our original This will remain the case during a transition period until we fully move the website to the new domain, at which time will start redirecting to Please note that HTTPS support has not yet been added to the new domain, so will fail to redirect but will succeed. This is only temporary and it is not a security concern because redirects are still sent to the secure

subscribe via RSS