-
Notifications
You must be signed in to change notification settings - Fork 521
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
[BUG] COCO export: Instance Segmentations OOB wrt their bounding box #2847
Comments
Hi, I'm a newbie in OSS and CV and I would like to contribute to this project. I made a pull request and I'm open to any feedback |
Is this issue completed or still open for contribution? |
Hi @DavidJimenez10 and @swamitagupta, thanks for offering to help. Yes, a contribution would be welcome! 🙌 The relevant code for importing/exporting in COCO format is in this module: In particular, the code that converts to COCO masks and back into FiftyOne masks is here: fiftyone/fiftyone/utils/coco.py Lines 2154 to 2214 in 2f5e53e
|
Is this issue still open? |
Instructions
Thank you for submitting an issue. Please refer to our issue policy for information on what types of issues we address.
System information
python --version
): 3.10.10fiftyone --version
): 0.20.0Commands to reproduce
Output:
Describe the problem
Exporting instance segmentations via COCODetectionDataset can result in segmentations that go out of bounds with respect to their bounding box by up to ~1.5px. This may cause an issue for some training pipelines and/or represent a small loss in accuracy.
I investigated one of the original COCO datasets downloaded from cocodataset.org and this issue was not present. So round-tripping through FO (importing and then re-exporting) likely causes the slight discrepancies.
What areas of FiftyOne does this bug affect?
App
: FiftyOne application issueCore
: Core Python library issueServer
: FiftyOne server issueWillingness to contribute
The FiftyOne Community encourages bug fix contributions. Would you or another member of your organization be willing to contribute a fix for this bug to the FiftyOne codebase?
The text was updated successfully, but these errors were encountered: