-
Notifications
You must be signed in to change notification settings - Fork 60
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
DataPack function to Retrieve overlapped ImageAnnotation using data structure grid #888
Comments
Actually, this is not what we discussed, we don't want users to manually compute any
|
Then maybe we should update the title and content of this issue. It should be targeted at implementing some internal algorithms for calculating overlap/covering between |
The prioritization of this item can be determined according to other items. This item is a stretch goal for the last quarter. Our final goal is to provide computation among arbitrary image annotations, and the defined goal for last quarter is for regular shapes only, like #802 |
I think currently our implementation can already compute overlapping between forte/forte/data/ontology/top.py Line 936 in 8a61272
For support like |
Yeah, that means we don't need the tutorial of how to do these for scratch, but it is valuable to show how to use these functions. For simple However, most of the supports for irregular shapes are not in our current scope, let's do them later. As for now, if operations involve those, we should throw some NotImplementedError. |
Is your feature request related to a problem? Please describe.
One of the main reasons for creating grid is to searching overlapped
ImageAnnotation
efficiently. However, the current code supports compute iou but not search overlappedImageAnnotation
.Describe the solution you'd like
ImageAnnnotation
given aImageAnnnotation
using the two dictionariesDescribe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
This is a follow-up issue on #876 (comment)
The text was updated successfully, but these errors were encountered: