-
Notifications
You must be signed in to change notification settings - Fork 340
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Added examples in documentation to mass_density and Hall_parame… #709
Conversation
Codecov Report
@@ Coverage Diff @@
## master #709 +/- ##
=======================================
Coverage 95.02% 95.02%
=======================================
Files 57 57
Lines 4722 4722
=======================================
Hits 4487 4487
Misses 235 235
Continue to review full report at Codecov.
|
Looks like this PR includes a bunch of commits from the asv benchmark PR; would you like me to clean it up for you? :) |
yes please , I dont know why that happened |
changelog file
That should do it! My best guess is that you stayed on your What you did is, by the way, a completely viable strategy when you're making a huge change that you'd prefer to break up into a few parts for easier, "staged" review. 😄 |
plasmapy/formulary/parameters.py
Outdated
>>> Hall_parameter(1e10 * u.m**-3, 2.8e3 * u.eV, 2.3 * u.T, 'He-4 +1') | ||
<Quantity 7.26446755e+16> | ||
>>> Hall_parameter(1e10 * u.m**-3, 5.8e3 * u.eV, 2.3 * u.T, 'He-4 +1') | ||
<Quantity 3.25995498e+17> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Tests seem to output the following value here:
<Quantity 3.25995498e+17> | |
<Quantity 2.11158408e+17> |
I may have messed the particle up while adding whitespace, didn't you have a proton or some such here before?
Anyway, it should be fine to keep it as it is and just modify the value :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I just pushed the change
I just deleted that branch, those commits are no longer showing up, is it because that branch is gone or you did something? |
I force-pushed to your branch due to AWESOME MAINTAINER POWERS, it shows up here if you scroll up:
I forgot to mention but you should now probably |
Or keep it deleted, since we're mostly done here! |
What I did locally, if you're interested, is:
Nothing like some git magic to start your day :D |
I'm having some errors during the test process (python setup.py test), |
|
|
Yeah, I left a suggestion above implementing that exact change - scroll up! I may have messed up the particle while working my git magic - apologies. |
not problem at all, Im running again tox. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good, thanks @diego7319 ! :)
Consider to update a documentation that tox is now a recommended way to run tests. I was dealing with outdated procedure described in documentation (http://docs.plasmapy.org/en/stable/development/testing_guide.html) before I came across with this post 😸 |
like this? assert 2 + 2 == 4, "Addition is broken. Reinstall universe and reboot." |
Yea, seems to be clear enough 👍 |
-Closes #708.
-Added examples to documentation to mass_density and Hall_parameter functions that were missing.
-Changed a ValueError in mass_density with a clearer message :
From : You must pass a particle (not None) to calculate the mass density!
to: If passing a number density, you must pass a particle (not None) to calculate the mass density!