---
tags: community, minutes
---

# PlasmaPy Community Meeting | Tuesday 2023 Jan 24 at 2 pm ET

### Video Conference Information
* [Zoom link](https://zoom.us/j/91633383503?pwd=QWNkdHpWeFhrYW1vQy91ODNTVG5Ndz09)
* [Element chat](https://app.element.io/#/room/#plasmapy:openastronomy.org)
* [GitHub Minutes Repository](https://github.com/PlasmaPy/plasmapy-project/tree/master/minutes)
* ["Community" Sub-directory](https://github.com/PlasmaPy/plasmapy-project/tree/master/minutes/_community)
* [Repository](https://github.com/PlasmaPy/plasmapy) ([pull requests](https://github.com/PlasmaPy/plasmapy/pulls), [issues](https://github.com/PlasmaPy/plasmapy/issues))
* [PlasmaPy Enhancement Proposals](https://github.com/PlasmaPy/PlasmaPy-PLEPs)
* [Calendar](https://calendar.google.com/calendar/embed?src=c_sqqq390s24jjfjp3q86pv41pi8%40group.calendar.google.com&ctz=America%2FNew_York)

## Agenda (please feel free to edit or add items)

[MPRL]: http://webhome.auburn.edu/~thomaed/mprl/mdpx-pages/mdpx-construction/construction-images-junejul/index.html
[ZEUS]: https://zeus.engin.umich.edu/laser/
[bridge]: http://ems-docs.element.io/books/element-cloud-documentation/page/discord-bridge
[SULI summer school]: https://suli.pppl.gov/2021/course/

1. Introductions
2. [Issues](https://github.com/PlasmaPy/PlasmaPy/issues)
- ...
3. [Pull requests](https://github.com/PlasmaPy/PlasmaPy/pulls)
- ...
4. dependabot
- dependabot handles one requirement at a time, while there are times when multiple requirements need to be updated together (like flake8)
6.
7.

## Attendees

* ...

## Action Items

***Person***
* ...

## Minutes

* maybe pull requests are too separated to be able to review things as a conceptual whole?
* *[A Philosophy of Software Design](https://www.amazon.com/dp/173210221X)*: number of lines of code less important than conceptual complexity
* [snapshottest](https://pypi.org/project/snapshottest/)

# current "test structure"
def test_formulary_function():
    inputs = ...
    outputs = gyrofrequency(*inputs)
    expected_output = 2.34234234235235 * u.rad / u.s
    u.testing.assert_quantity_allclose(expected_output, outputs)
    

# with snapshottest:
def test_formulary_function2(snapshot):
    inputs = ...
    outputs = gyrofrequency(*inputs)
    snapshot.match(outputs)
    # 1st run: generate csv/json
    # future runs: compares to existing csv/json
    # `pytest --snapshot-update` to regenerate

# and then you COULD (remains to be seen if useful) do:
@pytest.mark.parametrize("function_and_inputs", [
    (gyrofrequency, (inputs...))
    (gyroradius, (inputs...))
     ])
def test_formulary(snapshot,
                   function_and_inputs,
                   particle # comes from a fixture
                  ):
    inputs = ...
    outputs = function(*inputs)
    snapshot.match(outputs)
    # 1st run: generate csv/json
    # future runs: compares to existing csv/json
    # `pytest --snapshot-update` to regenerate
# could test it on plasma_dispersion_function?

- [ ] Dominik: where do we use `pytest-regressions` right now?
- [ ] add `pip-compile` and other administrative trivia bash calls to nox/tox/makefile
- schedule a zoom call with penguins for December
- [for Erik](https://www.youtube.com/watch?v=1NfxRkYtc-8)