Skip to content
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

Warning spam from pybnf dependencies #274

Open
emitra17 opened this issue Apr 3, 2019 · 6 comments
Open

Warning spam from pybnf dependencies #274

emitra17 opened this issue Apr 3, 2019 · 6 comments
Labels
good first issue Good for newcomers

Comments

@emitra17
Copy link
Collaborator

emitra17 commented Apr 3, 2019

Using fresh versions of all dependencies, with normalization enabled, the terminal gets spammed with many copies of the warning "data.py:304: RuntimeWarning: invalid value encountered in true_divide", presumably from a divide by 0 for some parameter sets.

@emitra17
Copy link
Collaborator Author

emitra17 commented Apr 3, 2019

Since we have a recurring issue of new package updates producing new unwanted output, it would be really nice to permanently solve this by suppressing all output except that generated by our printing module.

@emitra17
Copy link
Collaborator Author

+1 to needing to fix the general case.
Other offenders include YAMLLoadWarning and distributed.client "gather keys" errors. We've gotten reports from confused users worried these are affecting PyBNF performance.

Best case scenario would be to send stderr to the log instead of the terminal.

@emitra17 emitra17 changed the title Divide by 0 warning spam Warning spam from pybnf dependencies Jun 14, 2019
@emitra17 emitra17 added good first issue Good for newcomers and removed good for student labels Jun 27, 2019
@SauravMaheshkar
Copy link

@emitra17 can I take this up ? I'd love to contribute to the repository and this seems like a good place to start.

@wshlavacek
Copy link
Collaborator

wshlavacek commented Dec 17, 2021 via email

@SauravMaheshkar
Copy link

I ran pip install -U pybnf on a fresh colab instance and didn't see any of the aforementioned errors. Do these errors come up during editable installs ?

@wshlavacek
Copy link
Collaborator

wshlavacek commented May 17, 2022 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Good for newcomers
Projects
None yet
Development

No branches or pull requests

3 participants