You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A handful of pvlib functions often cause spit out runtime warnings for things like dividing by 0 or comparing the size of a nan value to a float. We should avoid or silence the warnings that we know are ok. They also make the test output a pain to read.
Here's a possibly incomplete list:
irradiance.perez divide by 0
irradiance.perez comparison with nan
clearsky.simplified_solis comparison with nan
pvsystem.sapm divide by 0 in log
pvsystem.ashraeiam comparison with nan
pvsystem.physicaliam comparison with nan
pvsystem.adrinverter comparison with nan
pvsystem.v_from_i overflow
I have some code ready for addressing the warnings in the perez model implementation. I'll post it soon.
I think the readability of the code suffers (in terms of being able to quickly see what math is being done) with some of the changes you propose. I sometimes disable certain warnings at the start of my scripts when they get on my nerves. Could that be adequate for other users? This suggestion could be put in the doc string for functions that are particularly annoying.
Uh oh!
There was an error while loading. Please reload this page.
A handful of pvlib functions often cause spit out runtime warnings for things like dividing by 0 or comparing the size of a nan value to a float. We should avoid or silence the warnings that we know are ok. They also make the test output a pain to read.
Here's a possibly incomplete list:
I have some code ready for addressing the warnings in the perez model implementation. I'll post it soon.Checked items are addressed in #429.
The text was updated successfully, but these errors were encountered: