tensorflow / tensorflow/models

visualization_export_dir not saving images to specified folder when used in eval_config{}

Open
#6,137 9 comments 1 reaction 3 assignees View on GitHub

@pkulzc is already working on this.

Since Jul 1, 2020.

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

Description

System information
  • What is the top-level directory of the model you are using: Object Detection
  • Have I written custom code (as opposed to using a stock example script provided in TensorFlow): NO
  • OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Linux Ubuntu 16.04
  • TensorFlow installed from (source or binary): binary
  • TensorFlow version (use command below): tf-nightly-gpu
  • Bazel version (if compiling from source):
  • CUDA/cuDNN version: 10/7.4
  • GPU model and memory: 2080ti x 2 and 32 gig ram
  • Exact command to reproduce:
The problem

As the title states, I would like to save the detection vs. ground truth images of the eval from Tensorboard.

From the eval proto:

// Path to directory to store visualizations in. If empty, visualization
// images are not exported (only shown on Tensorboard).
optional string visualization_export_dir = 6 [default=""];

Therefore I have added it to my model.config file as such. Keep in mind I am working from the /Object-Detection/ directory.

eval_config: {
  num_examples: 57

  visualization_export_dir: "bevelgear_training/eval_images/"
  num_visualizations: 57
  metrics_set: "pascal_voc_detection_metrics"
}

Training finishes as normal, I can see all the eval images in tensorboard BUT the "bevelgear_training/eval_images/ " folder is empty.

Am I overlooking something? Anyone get this working?

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.