The way `--output_coco_json` works right now is it operates on a dataset (which doesn't need to have ground truth). So you need to give a `--dataset` parameter instead of an `--image` parameter. The dataset you use doesn't need annotations, simply create a COCO dataset with just images and an empty annotation array and follow the dataset definition of `coco2017_testdev_dataset`.
See original GitHub issueHi, thanks for your code. it works well with my dataset. But I have a problem of outputting the json file of eval.py. I have create a json file with empty annotation based on the test image (more than one), so I used this json file on the coco2017_testdev_dataset, but it did not give a path for imaging, just path for json file. I think I did not really understand how I can use --dataset, can u explain more?? thanks a lot.
The way --output_coco_json
works right now is it operates on a dataset (which doesn’t need to have ground truth). So you need to give a --dataset
parameter instead of an --image
parameter. The dataset you use doesn’t need annotations, simply create a COCO dataset with just images and an empty annotation array and follow the dataset definition of coco2017_testdev_dataset
.
For single images, this is kind of cumbersome, but for large batches it probably works fine? This feature was intended for submission to the COCO eval servers so that’s why it’s so roundabout. Let me know if this is indeed too cumbersome, and I can add --output_coco_json
support to --image
.
_Originally posted by @dbolya in https://github.com/dbolya/yolact/issues/230#issuecomment-560542964_
Issue Analytics
- State:
- Created 2 years ago
- Comments:23
Top GitHub Comments
I modified the code and get the json file now.
the same as coco2017_testdev_dataset, and set ‘has_gt’ to False.