tensorflow / tensorflow/models

CenterNet MobileNetV2 FPN 512x512 erroneously configured for keypoint outputs

Open
#10,913 0 comments 0 reactions 1 assignee View on GitHub

@laxmareddyp is already working on this.

Since Jan 27, 2023.

models:research type:bug
Dominant language
Python
Stars
77.7k
Forks
44.8k
PR merge metrics
No merged PRs in 30d

Description

Prerequisites

Please answer the following questions for yourself before submitting an issue.

  • [ x] I am using the latest TensorFlow Model Garden release and TensorFlow 2.
  • [ x] I am reporting the issue to the correct repository. (Model Garden official or research directory)
  • [ x] I checked to make sure that this issue has not already been filed.

1. The entire URL of the file you are using

https://github.com/tensorflow/models/blob/master/research/object_detection/g3doc/tf2_detection_zoo.md
http://download.tensorflow.org/models/object_detection/tf2/20210210/centernet_mobilenetv2fpn_512x512_coco17_od.tar.gz

2. Describe the bug

Model "CenterNet MobileNetV2 FPN 512x512" is documented to use "boxes" as Outputs but pipeline.config file uses keypoints instead. Check line 120 and 137.

3. Steps to reproduce

Checkout pipeline.config at lines 120 and 137.

4. Expected behavior

Expect no num_keypoints to be present in this config.

5. Additional context

When training "CenterNet MobileNetV2 FPN 512x512" with given pipeline.config we see this error:
raise core._status_to_exception(e) from None # pylint: disable=protected-access
tensorflow.python.framework.errors_impl.InvalidArgumentError: {{function_node _wrappedIteratorGetNext_output_types_19_device/job:localhost/replica:0/task:0/device:GPU:0}} indices[0] = 0 is not in [0, 0)
[[{{node GatherV2_8}}]]
[[MultiDeviceIteratorGetNextFromShard]]
[[RemoteCall]] [Op:IteratorGetNext]

6. System information

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.