problem about Inference? about playground HOT 10 OPEN

@ranpin Hi, I did a quick run following the README instruction, and there was no coming issue.
Here is a screenshot using the predicted anno file.

Yes, it has no problem running. My confusion is :

1. the conut part in segmentation we get looks like garbled code, is this normal? Or is this coco's RLE format and it just looks like this with no problem?
2. is this json file is the standard coco format? Because the readme profile says that you do not generate coco.json files with annatation. But it has.

1. Yes, that's normal. These information may help you:
   (1) coco_style_eval.py
   (2) cocoapi issue#135
   (3) pycocotools source code
2. It is standard coco format.

ok, thank you. But, there is still a problem. You say that It is standard coco format. But due to the result of generated json cat_coco.json, it's not the same as the standard coco format. the category is not ture, i think it's better to keep align as well as the other categories.
the result of generated json cat_coco.json looks like this.
the standard coco format looks like this.

The categories depend on the cat/class_with_id.txt and you can customize your categories.

I find that cat/class_with_id.txt only clarify the categories. for example cat. Then, how can i modify related category id to "17 " and supercategory to "animal"?

Currently, it doesn't support this feature, you can change it in the source code in

from playground.

@ranpin Did you solve the problem?

from playground.

@ranpin Did you solve the problem?

No, I didn't. Nobady discussed with me.

from playground.

@ranpin Hi, I did a quick run following the README instruction, and there was no coming issue.

Here is a screenshot using the predicted anno file.

from playground.

@ranpin Hi, I did a quick run following the README instruction, and there was no coming issue.

Here is a screenshot using the predicted anno file.

Yes, it has no problem running. My confusion is :

1. the conut part in segmentation we get looks like garbled code, is this normal? Or is this coco's RLE format and it just looks like this with no problem?
2. is this json file is the standard coco format? Because the readme profile says that you do not generate coco.json files with annatation. But it has.

from playground.

@ranpin Hi, I did a quick run following the README instruction, and there was no coming issue.
Here is a screenshot using the predicted anno file.

Yes, it has no problem running. My confusion is :

1. the conut part in segmentation we get looks like garbled code, is this normal? Or is this coco's RLE format and it just looks like this with no problem?
2. is this json file is the standard coco format? Because the readme profile says that you do not generate coco.json files with annatation. But it has.

1. Yes, that's normal. These information may help you:
   (1) coco_style_eval.py
   (2) cocoapi issue#135
   (3) pycocotools source code
2. It is standard coco format.

from playground.

@ranpin Hi, I did a quick run following the README instruction, and there was no coming issue.
Here is a screenshot using the predicted anno file.

Yes, it has no problem running. My confusion is :

1. the conut part in segmentation we get looks like garbled code, is this normal? Or is this coco's RLE format and it just looks like this with no problem?
2. is this json file is the standard coco format? Because the readme profile says that you do not generate coco.json files with annatation. But it has.

1. Yes, that's normal. These information may help you:
   (1) coco_style_eval.py
   (2) cocoapi issue#135
   (3) pycocotools source code
2. It is standard coco format.

ok, thank you. But, there is still a problem. You say that It is standard coco format. But due to the result of generated json cat_coco.json, it's not the same as the standard coco format. the category is not ture, i think it's better to keep align as well as the other categories.

the result of generated json cat_coco.json looks like this.

the standard coco format looks like this.

from playground.

@ranpin Hi, I did a quick run following the README instruction, and there was no coming issue.
Here is a screenshot using the predicted anno file.

Yes, it has no problem running. My confusion is :

1. the conut part in segmentation we get looks like garbled code, is this normal? Or is this coco's RLE format and it just looks like this with no problem?
2. is this json file is the standard coco format? Because the readme profile says that you do not generate coco.json files with annatation. But it has.

1. Yes, that's normal. These information may help you:
   (1) coco_style_eval.py
   (2) cocoapi issue#135
   (3) pycocotools source code
2. It is standard coco format.

ok, thank you. But, there is still a problem. You say that It is standard coco format. But due to the result of generated json cat_coco.json, it's not the same as the standard coco format. the category is not ture, i think it's better to keep align as well as the other categories.

the result of generated json cat_coco.json looks like this.

the standard coco format looks like this.

The categories depend on the cat/class_with_id.txt and you can customize your categories.

from playground.

@ranpin Hi, I did a quick run following the README instruction, and there was no coming issue.
Here is a screenshot using the predicted anno file.

Yes, it has no problem running. My confusion is :

1. the conut part in segmentation we get looks like garbled code, is this normal? Or is this coco's RLE format and it just looks like this with no problem?
2. is this json file is the standard coco format? Because the readme profile says that you do not generate coco.json files with annatation. But it has.

1. Yes, that's normal. These information may help you:
   (1) coco_style_eval.py
   (2) cocoapi issue#135
   (3) pycocotools source code
2. It is standard coco format.

ok, thank you. But, there is still a problem. You say that It is standard coco format. But due to the result of generated json cat_coco.json, it's not the same as the standard coco format. the category is not ture, i think it's better to keep align as well as the other categories.
the result of generated json cat_coco.json looks like this.
the standard coco format looks like this.

The categories depend on the cat/class_with_id.txt and you can customize your categories.

I find that cat/class_with_id.txt only clarify the categories. for example cat. Then, how can i modify related category id to "17 " and supercategory to "animal"?

from playground.

@ranpin Hi, I did a quick run following the README instruction, and there was no coming issue.
Here is a screenshot using the predicted anno file.

Yes, it has no problem running. My confusion is :

1. the conut part in segmentation we get looks like garbled code, is this normal? Or is this coco's RLE format and it just looks like this with no problem?
2. is this json file is the standard coco format? Because the readme profile says that you do not generate coco.json files with annatation. But it has.

1. Yes, that's normal. These information may help you:
   (1) coco_style_eval.py
   (2) cocoapi issue#135
   (3) pycocotools source code
2. It is standard coco format.

ok, thank you. But, there is still a problem. You say that It is standard coco format. But due to the result of generated json cat_coco.json, it's not the same as the standard coco format. the category is not ture, i think it's better to keep align as well as the other categories.
the result of generated json cat_coco.json looks like this.
the standard coco format looks like this.

The categories depend on the cat/class_with_id.txt and you can customize your categories.

I find that cat/class_with_id.txt only clarify the categories. for example cat. Then, how can i modify related category id to "17 " and supercategory to "animal"?

Currently, it doesn't support this feature, you can change it in the source code in

playground/mmdet_sam/images2coco.py

Line 63 in 531e1cf

category_item['supercategory'] = 'none'

playground/mmdet_sam/images2coco.py

Line 64 in 531e1cf

category_item['id'] = int(category_id)

ok, thank you. I have no problem. But I still hope that you can support it some day. This will bring great convenience to our ordinary users.Thanks again！

from playground.