-
Notifications
You must be signed in to change notification settings - Fork 133
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
Shut up the RuntimeWarnings during fitting #25
Comments
Should I safely ignore these warnings as long as a fit is produce? Which would be the error when the package fail to produce a good fit and, then, I should discard the result? Is it possible at all that the program fail generating an appropriate fit? I don't really mind the warning as long as there is an accompanying message indicated that the package successfully generated the fit. |
You can ignore the warnings as long as there's a fit. As long as the On Wed, Oct 7, 2015 at 8:46 PM, Roberto notifications@github.com wrote:
|
Hey, that was quick. Thanks a lot. |
Hey @jeffalstott, thanks for making this. Related question: can I shut up the message: |
Hi @albertocottica, I've just added an option to |
It would be really nice if the fix for the above is released on PyPi. I'm running the powerlaw fittings on thousands of distributions and seeing that many "Calculating..." messages clogging the screen and drowning out all other application messages is no fun. Thank you! |
@trungdong Done. |
During fitting we frequently explore fits that are outside our numerical precision. This can lead to weird events like dividing by zero when we really mean to divide by a very small number. These explored fits are never taken to be good fits, and so they aren't used for the final results returned to the user. However, during the fitting we still get RuntimeWarnings when these errors occur. Like this:
Is there a good way to stop these warnings from appearing without just making a blanket setting that we don't want to see any warnings?
The text was updated successfully, but these errors were encountered: