tensorflow / tensorflow/models
Inference TF2 Tutorial "PATH_TO_BE_CONFIGURED" and model name mismatch error.
@pkulzc is already working on this.
Since Aug 27, 2020.
- Dominant language
- Python
- Stars
- 77.7k
- Forks
- 44.8k
- PR merge metrics
- No merged PRs in 30d
Description
Prerequisites
Please answer the following question for yourself before submitting an issue.
- I checked to make sure that this issue has not been filed already.
1. The entire URL of the documentation with the issue
2. Describe the issue
For this Colab tutorial I tried to run all the cells but it gives an error at the line configs = config_util.get_configs_from_pipeline_file(pipeline_config)
However I figured out the problem:
In tutorial name of the model is called as
centernet_hg104_512x512_kpts_coco17_tpu-32
but in models/research/object-detection/configs/tf2 folder, where pipeline_config = os.path.join('models/research/object_detection/configs/tf2/', model_name + '.config') statement in the tutorial addresses, the name of the file corresponding that network is ... _hourglass104 _ ... rather than ... _hg104 _....
Then I changed the model_name variable then it worked.
However, I now encountered a new problem that I couldn't fix:
The configuration files in the models/research/object-detection/configs/tf2 directory contains flags called PATH_TO_BE_CONFIGURED ( Check this out.)
Thus, at the label_map = label_map_util.load_labelmap(label_map_path) statement from the tutorial,
NotFoundError: PATH_TO_BE_CONFIGURED/label_map.txt; No such file or directory error arises.
There are also some spaces filled with ????. I couldn't figure them out either. (Check this out.)
Should the API or system environment fill that automatically or I would be the one filling it ? If so, how ?
I couldn't find any file describing that flag (PATH_TO_BE_CONFIGURED) or a issue containing.
Best regards.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.