Test for continuity of results with direct shading #91
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Noticed that
pvfactorsbefore v1.3.0 had a small discontinuity in predictions when direct shading happened. This is probably due to the fact that ground shadow surfaces used to get merged together when direct shading happened, and some small error probably occurred there.In
pvfactorsstarting at v1.3.0, the results are more continuous (and there's a perfect match with previous versions when there's no direct shading), which indicates that it's probably more accurate.--> Implement a test that takes a snapshot of that continuity, and which makes sure it's always conserved.