-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix alpha shape #87
Open
bertsky
wants to merge
87
commits into
cisocrgroup:master
Choose a base branch
from
bertsky:fix-alpha-shape
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Fix alpha shape #87
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
This pull request introduces 1 alert when merging 200313f into a30ce3b - view on LGTM.com new alerts:
|
This was referenced Mar 24, 2022
This pull request introduces 1 alert when merging b64e66a into a30ce3b - view on LGTM.com new alerts:
|
bertsky
force-pushed
the
fix-alpha-shape
branch
from
March 25, 2022 11:30
b64e66a
to
5c362e2
Compare
dammit, 8841abc contains accidentally commited parts that crash |
bertsky
force-pushed
the
fix-alpha-shape
branch
from
March 25, 2022 14:34
5c362e2
to
2cdfa79
Compare
…cs/punctuation, too
instead of detecting hlines and vlines independently, and via costly horizontal/vertical morphology operations, analyse image by medial axis transform (skeleton and distance transform of all connected components); then filter components that are too compact (inner vs outer size), also filter by statistics of distance along the skeleton: filter if too wide on average or too variant; then apply morphological closing to reconnect broken segments, linking only those components that roughly extend each other in the same direction; finally, sort by size and filter components that are too small in inner (skeleton length) or outer size (bbox diagonal), selecting only the topmost candidates; propagate from skeleton to full component and then spread a little into the background
…gradient maximum and percentile
Update dockerfile
…nore extend_margins
This was
linked to
issues
Jul 31, 2024
fix: levenshtein import (follow-up to 5282092)
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.
Some early fixes for the recent #77 – sorry to get back to you so soon @finkf (and thanks for merging so fast).
BTW, if you contemplate making a new release, here is a list of things that have changed since 0.1.5: