Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • 16:48
    namurphy labeled #1276
  • 16:47
    namurphy labeled #1277
  • 16:47
    namurphy labeled #1277
  • 16:47
    namurphy labeled #1277
  • 16:47
    namurphy opened #1277
  • 16:42
    namurphy opened #1276
  • 16:42
    namurphy labeled #1276
  • 16:42
    namurphy labeled #1276
  • Sep 21 23:54

    namurphy on main

    Update documentation guide on g… (compare)

  • Sep 19 23:41
    namurphy labeled #1265
  • Sep 19 23:40
    namurphy labeled #1265
  • Sep 19 23:40
    namurphy labeled #1270
  • Sep 19 23:40
    namurphy unlabeled #1270
  • Sep 19 22:50
    namurphy edited #1270
  • Sep 19 22:00
    namurphy edited #1270
  • Sep 19 21:59
    namurphy edited #1270
  • Sep 19 21:49
    namurphy edited #1270
  • Sep 19 20:07
    namurphy milestoned #1271
  • Sep 19 20:00
    namurphy milestoned #1270
  • Sep 19 20:00
    namurphy labeled #1270
Dominik Stańczak
@StanczakDominik:matrix.org
[m]
I'd love to dig into it and have it implemented in a few days, but, you know, thesis deadlines. 😅
Julien Hillairet
@jhillairet:matrix.org
[m]
;)
nitisha
@nitisha:matrix.org
[m]
Hey all, I'm learning to use the plasmapy package and don't have a lot of plasma physics knowledge. Are there any examples I can follow for creating objects like Quantity and UnitBase to use them in computations?
Nick Murphy
@namurphy:matrix.org
[m]
Probably the first place to look would be Astropy's documentation on units and quantities. I'd expect that there are some Jupyter notebooks out there on units and quantities too, which I'll post here if I can find any.
And a friendly reminder that we'll be having our weekly community meeting in about ten minutes at 19 UTC at the usual Jitsi link.
1 reply
digitalextremist
@digitalextremist:matrix.org
[m]
Very excited to get up to speed on PlasmaPy and contribute! Digging in after a long stream of recommendations leading me here.
Dominik Stańczak
@StanczakDominik:matrix.org
[m]
Happy to hear that! Feel free to poke if we can help in any way :)
1 reply
Nick Murphy
@namurphy:matrix.org
[m]

I'm going to be giving a tutorial on Monday on writing clean code. It's being organized through the library at my institution, but I asked and it's okay for people from elsewhere to join in.

Writing Clean Scientific Software
Monday, March 15th, 2-3pm EDT (18 UTC)
Presented by Nick Murphy

Register here

The Zoom link (and an email reminder) will be emailed to registrants after signing up.

Description
Software is vital to modern science. It's hard to think of an astronomical research project that does not make use of software in some fundamental way. But despite how foundational software is to our research, graduate programs in science have tended to lack coursework in research software engineering. Because of this, scientists often end up having to write code without any formal training. This tutorial will cover best practices for writing research software that is readable, maintainable, and thus easier to change. Some of the topics will include choosing meaningful variable names, writing clean functions, separating high-level big picture code from low-level implementation details, and writing clean tests. This tutorial will encourage us to think of code as communication.

aarrcchhiimmeeddeess
@aarrcchhiimmeeddeess:matrix.org
[m]
Hi, everyone. I am new to Python (I did some Pascal programming before, though) and I stumbled upon PlasmaPy.
I wonder (and did not found a clear answer yet) how it is with low temperature plasma in PlasmaPy?
My primary interests are non-equilibrium discharge plasmas (ionization degree<<1), magnetron sputtering, plasma etching&deposition, dusty ("complex") plasma and molecular plasma chemistry.
rocco8773
@rocco8773:matrix.org
[m]
Hi aarrcchhiimmeeddeess , welcome to PlasmaPy! Thank you for dropping by. We have yet to add much functionality related to low temperature plasmas. We haven't had contributors specialized in that area come through, so not much has been contributed. But we'd like to see that change. If there's any functionality you would like, then please open an issue or, if you feel ambitious, contribute a pull request. Functionality for PlasmaPy is primarily driven by the community's wants, so the more a feature is requested then the quicker it will get into PlasmaPy.
1 reply
rocco8773
@rocco8773:matrix.org
[m]
Correct. Just hit the "New Issue" button and describe the feature you'd like added it PlasmaPy. If you have any reference material, then that would be much appreciated. As I previously said, none of the core developers are specialists in low temp plasmas, so reference materials would be very helpful for us. Thanks!
Dominik Stańczak
@StanczakDominik:matrix.org
[m]
I'll just point that if you or others make 1000 requests for feature X which none of the active contributors know anything about, we might want it more but the chances for its quick inclusion are still pretty low! 😞
Dominik Stańczak
@StanczakDominik:matrix.org
[m]
Nick Murphy
@namurphy:matrix.org
[m]
Awesome! Many thanks to everyone who contributed! And to Dominik Stańczak, rocco8773, peterheuer, and tiger-du for all of the updates/code reviews over the last week or two.
rocco8773
@rocco8773:matrix.org
[m]
Dominik Stańczak: Awesome! Thank you for putting in the final leg work to get us over the line. Much appreciated!!
rocco8773
@rocco8773:matrix.org
[m]
Dominik Stańczak: For ease of maintenance, what do you think of replacing the contents of CHANGELOG.rst with a link to the change log page of RTD? You'd probably want to also make CHANGELOG a markdown file as well.
1 reply
rocco8773
@rocco8773:matrix.org
[m]
:point_up: Edit: Dominik Stańczak: For ease of maintenance, what do you think of replacing the contents of CHANGELOG.rst with a link to the change log page on RTD? You'd probably want to also make CHANGELOG a markdown file as well.
:point_up: Edit: Dominik Stańczak: For ease of maintenance, what do you think of replacing the contents of CHANGELOG.rst with a link to the change log page on RTD? You'd probably want to also make CHANGELOG a markdown file.
Cadair
@cadair:cadair.com
[m]
Isn't the changelog page on RTD built from CHNAGELOG.rst?
Dominik Stańczak
@StanczakDominik:matrix.org
[m]
Not yet, at least; at this point our RTD doesn't build a central changelog page, it just builds ones per each release. It probably should, and it probably live https://docs.plasmapy.org/en/stable/whatsnew/index.html here just below the per-release page links... or we should probably look at how y'all do that over on the sunnier side. I'll jump on that later.
Cadair
@cadair:cadair.com
[m]
Fair enough, they are all subheadings in the main rst file for us
namurphy
@namurphy:matrix.org
[m]
Oh. Huh. I forgot that we still need to decide on the time of our meeting today (given that the change to DST happened in the US). Want to say 18 UTC / 7 pm CET / 2 pm EDT / 11 am PDT?
I've got no other conflicts today so anytime works for me.
Nick Murphy
@namurphy:matrix.org
[m]
Sounds good! Let's plan on 18 UTC today at our usual Jitsi link.
And here's a link to our agenda & minutes doc.
rocco8773
@rocco8773:matrix.org
[m]
I have my GAPS meeting today, so I might be a few minutes late to the community meeting.
Nick Murphy
@namurphy:matrix.org
[m]
Sure, no problem at all.
Nick Murphy
@namurphy:matrix.org
[m]
I've been thinking that it'd be helpful to have some low barrier to entry projects that people could work on for the hack week. One possibility would be to ask participants to create user stories that are related to their research. We could collect the users stories for plasma research and education, and upload them to Zenodo, with all of contributors being listed as authors. The benefit of this is that it'd give a way for people to get involved in a way that would be really helpful for us (and potentially other plasma software projects) without having to do anything with code.
1 reply
Dominik Stańczak
@StanczakDominik:matrix.org
[m]
Hey everyone, here's a friendly timezone adjusted reminder that (I think we're supposed to be) having our weekly community meeting in an hour from now, with the agenda link https://hackmd.io/@plasmapy/B1thRPIVu/edit here, at the usual jitsi link: https://meet.jit.si/plasmapy
Dominik Stańczak
@StanczakDominik:matrix.org
[m]
Hey everyone, here's a reminder that we're having our weekly community meeting in half an hour from now, with the agenda link https://hackmd.io/@plasmapy/rkxHI1OE_/edit here, at the usual jitsi link: https://meet.jit.si/plasmapy
Julien Hillairet
@jhillairet:matrix.org
[m]

I'm going to be giving a tutorial on Monday on writing clean code. It's being organized through the library at my institution, but I asked and it's okay for people from elsewhere to join in.

Writing Clean Scientific Software
Monday, March 15th, 2-3pm EDT (18 UTC)
Presented by Nick Murphy

Register here

The Zoom link (and an email reminder) will be emailed to registrants after signing up.

Description
Software is vital to modern science. It's hard to think of an astronomical research project that does not make use of software in some fundamental way. But despite how foundational software is to our research, graduate programs in science have tended to lack coursework in research software engineering. Because of this, scientists often end up having to write code without any formal training. This tutorial will cover best practices for writing research software that is readable, maintainable, and thus easier to change. Some of the topics will include choosing meaningful variable names, writing clean functions, separating high-level big picture code from low-level implementation details, and writing clean tests. This tutorial will encourage us to think of code as communication.

Dear Nick,
Was it a powerpoint presentation or a live demo? (Or maybe a bit of both?). I would be interest if it could eventually be shared.

Nick Murphy
@namurphy:matrix.org
[m]
It was a presentation this time, though I've been meaning to incorporate some interactive exercises too. I have an earlier version of the clean code slides up on Zenodo, which I'll probably be updating within a few months.
Julien Hillairet
@jhillairet:matrix.org
[m]
Thanks!

Particularly the following (~pg 107)

"""
For the most part, computation remains the province of experts. Most noncommercial
simulation codes are primarily used by their developers and a small
cohort that can be supported by direct access to the developers.

Finding: Plasma simulation is not optimally accessible to the wide range of
potential users, including experimentalists and industrial users.

As more sophisticated hardware becomes available in the exascale era, codes
that were developed using older technologies face an increasing technology gap
and need to be ported to new architectures.

Finding: Funding agencies have not traditionally supported code usability to
the extent needed to make research codes user-friendly, support users of codes,
or to transition existing codes to new computing architectures.

Recommendation: Funding agencies, and in particular DOE and NSF, should
support mechanisms for making computational plasma software more
widely accessible to noncomputing experts, and to transition current codes
to new computing architectures.

For example, these agencies should examine the role for public-private partnerships
that could make easily used software available on agency computers. In
this regard, to make the broadest impact, open source software being sponsored
by NSF and DOE should be accessible to the nonexperts and useable on a broad
range of computing architectures.

Finding: Funding agencies have not traditionally supported code usability to
the extent needed to make research codes user-friendly, support users of codes,
or to transition existing codes to new computing architectures.

Recommendation: Funding agencies, and in particular DOE and NSF, should
support mechanisms for making computational plasma software more
widely accessible to noncomputing experts, and to transition current codes
to new computing architectures.

The preceding finding is becoming an even greater need as more of computational
plasma physics transitions to a situation where fewer but more widely
accessible codes exist, each with many users who are not necessarily the developers.

Recommendation: Computational plasma science and engineering, supported
by NSF, should include projects for writing textbooks and developing
courses to train the current and next generation of computational
plasma scientists, and to enable noncomputer experts to make optimal use
of computations.

"""

David Schaffner
@dschaffner:matrix.org
[m]
It's a good thing they had a PlasmaPy guy on the committee
peterheuer
@peterheuer:matrix.org
[m]
That explains it then: very nice!
Nick Murphy
@namurphy:matrix.org
[m]
Holy hopping rutabagas, I forgot about the recommendation about writing textbooks and developing courses for training computational plasma scientists. I agree with that 100%!
1 reply
David Schaffner
@dschaffner:matrix.org
[m]
peterheuer: Troy has been very receptive to PlasmaPy, but to be fair, the whole committee was quite receptive to many of the ideas that people like Nick advocated for
Peter Heuer
@peterheuer:matrix.org
[m]
That's excellent!
Nick Murphy
@namurphy:matrix.org
[m]
I guess the 47851 papers we wrote were worth it then.
1 reply
And now the heliophysics decadal survey in the US is coming up soon too...which means a whole bunch more papers!
1 reply
...but thankfully there are others in the helio community who have taken the lead on things like that.
Not that I know of. And I'm also hoping they'll be doing something like in astronomy where they have a "state of the profession" panel as well as a science panel.
David Schaffner
@dschaffner:matrix.org
[m]
I'm looking forward to Astro2020...I hope having Ellen and Elliot on the committee will be helpful for plasma in general
Nick Murphy
@namurphy:matrix.org
[m]
For the plasma decadal...the charge neglected to mention anything directly related to diversity, equity, and inclusion, so the recommendations for that got pushed into an appendix since the committee still viewed it as extremely important.
David Schaffner
@dschaffner:matrix.org
[m]
Similar to what happened with the DOE LRP
Nick Murphy
@namurphy:matrix.org
[m]
Yeah...I'm hopeful for Astro2020, give or take a year
David Schaffner
@dschaffner:matrix.org
[m]
Just imagine how big PlasmaPy will be for Plasma2030