wip: experimenting with pixel prediction on 4-connected #65
Conversation
This file contains hidden or 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
william-silversmith
changed the title
william-silversmith
force-pushed
the
master
branch
from
40c3c29 to
9943790
Compare
william-silversmith
force-pushed
the
master
branch
2 times, most recently
from
2292fec to
d8d56df
Compare
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.
Got it working but it's slower than the regular decision tree. The simplicity of 4 connected might mean the extra code size and jumping around isn't worth it compared to the smaller opportunities for savings. My gut says 6-connected would do better (3 useful predictions vs 2). However, I could also have just made subtle mistakes too.