-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Correct condition 5 in clearsky.detect_clearsky
#506
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
Comments
If I understand correctly, the pvlib code is essentially:
but Reno and Hansen describe:
It would be good to include an example/test where this changes the overall result. |
@wholmgren you understand correctly. Do we need to test before/after when fixing a bug though? |
Perhaps not in general, but in this case it sound like the published results may have been based on code with a bug, so technically you should perhaps run the corrected code, check the results and publish an erratum. |
@cwhanse my feeling is that the detect_clearsky_data.csv test data should include values that produce a different test result when the code is changed. |
Of course, I agree that we should correct the test along with the code fix. I can publish a comparison on pvpmc.sandia.gov, or post the results here. |
Describe the bug
Condition 5 in
clearsky.detect_clearsky
does not agree with Eq. 12 - 14 of the reference. See #505Expected behavior
clearsky.detect_clearsky
currently calculates condition 5 as the difference in maximum absolute slopes, rather than the maximum of the absolute differences in slopes.Versions:
pvlib.__version__
: 0.5The text was updated successfully, but these errors were encountered: