Ilastik/predict #18
Merged
Ilastik/predict #18
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
|
There are some weird extra commits here. The only necessary commits are the last two. |
mcquin
reviewed
Aug 21, 2017
|
I think I messed stuff up. Should I cancel this pull request and start over? |
|
@karhohs I don't think that's necessary. I can help you untangle the git history in the office tomorrow. |
karhohs
force-pushed
the
ilastik/predict
branch
from
3b986b2
to
8ef167e
Compare
mcquin
force-pushed
the
ilastik/predict
branch
from
6f480df
to
3724c8b
Compare
karhohs
force-pushed
the
ilastik/predict
branch
from
8ef167e
to
fd917f7
Compare
mcquin
approved these changes
Aug 22, 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.
I added the ability to use the Autocontext ilastik project in addition to the Pixel Classification.