tensorflow / tensorflow/models

NotFoundError: models/research/object_detection/configs/tf2/centernet_hg104_512x512_kpts_coco17_tpu-32.config; No such file or directory

Open
#8,839 6 comments 15 reactions 3 assignees View on GitHub

Nobody has claimed this yet.

models:research:odapi 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.

  • [+] I am using the latest TensorFlow Model Garden release and TensorFlow 2.
  • [+] I am reporting the issue to the correct repository. (Model Garden official or research directory)
  • [+] 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/colab_tutorials/inference_tf2_colab.ipynb

2. Describe the bug

NotFoundError: models/research/object_detection/configs/tf2/centernet_hg104_512x512_kpts_coco17_tpu-32.config; No such file or directory when trying to execute the above mentioned notebook with Google Colab

3. Steps to reproduce

Run the above mentioned notebook in Google Colab.

4. Expected behavior

Configuration should be found and loaded in.

5. Additional context

The problem results from the following line:

pipeline_config = os.path.join('models/research/object_detection/configs/tf2/', model_name + '.config')

where model_name is either centernet_hg104_512x512_kpts_coco17_tpu-32 or centernet_hg104_512x512_coco17_tpu-8.

There are no files with that name inside the config/tf2 folder, but there are two other config files center_net_hourglass104_1024x1024_coco17_tpu-32.config and center_net_hourglass104_512x512_coco17_tpu-8.config, which work for the model but they don't have a labelmap defined. Therefore the labelmap can't be loaded by saying configs['eval_input_config'].label_map_path. Rather the path must be manually specified.

6. System information

Google Colab

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.