You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the 'examples/analyzing-object-detection-dataset.ipynb' there is claimed that FastDUP can read COCO json files and convert them to the FastDUP format: "fastdup requires the annotations to be in a specific format. We will use a simple converter to convert the COCO format JSON annotation file into the fastdup annotation dataframe. This converter is applicable to any dataset that uses the COCO format." However, the file they load is not json but CSV and the format specified cannot handle multiple bounding boxes and segmentations. A feature that provides compatibility with a real COCO json file would be valuable.
Each row on the dataframe represents one bounding box annotation. If there are multiple boxes for each image, you will see multiple rows on the dataframe with difference bounding box coordinates but with the same filename.
It seems that the COCO is correctly loaded in the DataFrame indeed. However, when i run fd.explore(), I see no annotations in the webserver gallery. The gallery exist of separate folders of images with 'No labels available'. Also no objects are available. So can I also analyze annotations in the visualizer?
Feature Name
Real COCO Compatibility
Feature Description
In the 'examples/analyzing-object-detection-dataset.ipynb' there is claimed that FastDUP can read COCO json files and convert them to the FastDUP format: "fastdup requires the annotations to be in a specific format. We will use a simple converter to convert the COCO format JSON annotation file into the fastdup annotation dataframe. This converter is applicable to any dataset that uses the COCO format." However, the file they load is not json but CSV and the format specified cannot handle multiple bounding boxes and segmentations. A feature that provides compatibility with a real COCO json file would be valuable.
Contact Information [Optional]
[email protected]
The text was updated successfully, but these errors were encountered: