Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • 00:51
    namurphy labeled #1172
  • 00:51
    namurphy labeled #1172
  • 00:51
    namurphy labeled #1172
  • 00:51
    namurphy opened #1172
  • Jun 21 18:02

    pheuer on main

    Input ion velocity in thomson n… (compare)

  • Jun 16 21:07
    namurphy edited #1170
  • Jun 16 21:07
    namurphy edited #1169
  • Jun 16 21:05
    namurphy labeled #1170
  • Jun 16 21:05
    namurphy labeled #1170
  • Jun 16 21:05
    namurphy opened #1170
  • Jun 16 21:05
    namurphy labeled #1170
  • Jun 16 20:58
    namurphy labeled #1169
  • Jun 16 20:58
    namurphy labeled #1169
  • Jun 16 20:58
    namurphy labeled #1169
  • Jun 16 20:58
    namurphy opened #1169
  • Jun 11 11:21

    StanczakDominik on github_actions

    (compare)

  • Jun 11 11:21

    StanczakDominik on main

    Bump codecov/codecov-action fro… (compare)

  • Jun 09 06:25

    dependabot[bot] on github_actions

    Bump codecov/codecov-action fro… (compare)

  • Jun 03 23:55
    namurphy labeled #1167
  • Jun 03 23:55
    namurphy opened #1167
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
Dominik Stańczak
@StanczakDominik:matrix.org
[m]
Looking forward to showcasing v1.0.2 there! ;)
Nick Murphy
@namurphy:matrix.org
[m]
Yeah, I'm extremely hopeful. I'm thinking of how Python picked up in solar physics. SunPy started in maybe 2012, and in the recent small number of years, it's really gotten a lot more widely used. The solar community is in a large-scale shift from IDL to Python.
It does take time for there to be a community-wide change...but we will keep pushing for it.
David Schaffner
@dschaffner:matrix.org
[m]
*broad
Nick Murphy
@namurphy:matrix.org
[m]
Yeah, that's been a great discussion...though unfortunate that the DPP Engage forum is only viewable by DPP members.
Peter Heuer
@peterheuer:matrix.org
[m]
Agreed: that thread is great! But I agree probably many people don't read that forum.
David Schaffner
@dschaffner:matrix.org
[m]
Right, but it's something that we are in a position to address and promote
Perhaps even bring up to some extent during Hack week
Nick Murphy
@namurphy:matrix.org
[m]
Oh — that also reminds me. The US Research Software Engineer Association (US-RSE) had its first working group meeting on education and training today. It's just getting started, but I'm hoping that it'll be helpful to partner with them in the future.
Peter Heuer
@peterheuer:matrix.org
[m]
Maybe a more formal survey (eg. a Google form) to collect information similar to Nick's thread on computational education would produce more compact results that could more easily be disseminated? We did something similar after a recent diagnostics conference to collect statistics on which languages and codes were being used.
Nick Murphy
@namurphy:matrix.org
[m]
That would indeed be helpful.
I've also been thinking now and then about a survey that focuses on what functionality the plasma community would find useful.
Dominik Stańczak
@StanczakDominik:matrix.org
[m]
Hey everyone, here's a friendly reminder that we've got our weekly community meeting in 35min, with the minutes here and the usual Jitsi link here :)
SolarDrew
@solardrew:openastronomy.org
[m]
how come?
Dominik Stańczak
@StanczakDominik:matrix.org
[m]
jitsi had issues with Erik's screen share
and was just being all around unstable today :(
SolarDrew
@solardrew:openastronomy.org
[m]
aah ok, not permanently?
Dominik Stańczak
@StanczakDominik:matrix.org
[m]
yeah, hopefully
SolarDrew
@solardrew:openastronomy.org
[m]
fair enough
Nick Murphy
@namurphy:matrix.org
[m]
Yeah, I'm not sure why screen sharing on Jitsi was grumpy today.
David Schaffner
@dschaffner:matrix.org
[m]
Frankly, I think this board is to negative about our corporate Zoom overlords