Introduce precise drawing algorithm #99
Merged
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
tboch
approved these changes
Aug 2, 2017
|
🎉 |
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.
As discussed in #98 and #84, I have introduced the precise drawing using a boolean named
precise, which defaults toFalsefor now. The result can be seen on this notebook: https://github.com/adl1995/HIPS-to-Py/blob/master/examples/Precise drawing.ipynbI have copied the resulting images below as well. Precise drawing:
Simple drawing:
Although the results are not apparent here, they can clearly be seen when viewed through an image viewer. Also currently there is no recursion involved. @tboch Please take a look.