Fixed bug in multitarget macenko during import#64
Merged
carloalbertobarbano merged 6 commits intoEIDOSLAB:developmentfrom Jan 13, 2025
Merged
Fixed bug in multitarget macenko during import#64carloalbertobarbano merged 6 commits intoEIDOSLAB:developmentfrom
carloalbertobarbano merged 6 commits intoEIDOSLAB:developmentfrom
Conversation
Update citation
fix tests badge
Collaborator
Author
|
Any thoughts on this @desi-ivanov? Do you have a small code snippet showing how to use it? Currently, I just get an error when I use it on simple example images. |
Closed
Member
|
I'll merge the PR and take a look at the bug |
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
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.
Doing this was producing an error:
But after these changes, it is possible to use as with any other normalizer.
However, I am struggling to understand how to use it properly, as it just seem to crash all the time, but that can be handled in a separate issue/PR.