tensorflow / tensorflow/models

[object_detection] non-determinism within the training

Open
#8,022 0 comments 0 reactions 3 assignees View on GitHub

@pkulzc is already working on this.

Since May 29, 2020.

models:research:odapi type:bug
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: models-master/research/object_detection/
  • Have I written custom code (as opposed to using a stock example script provided in TensorFlow): yes but mostly print statements inside the core code
  • OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Ubuntu 16.04
  • TensorFlow installed from (source or binary): binary, installed from pip: pip install tensorflow-gpu
  • TensorFlow version (use command below): 1.14
  • Bazel version (if compiling from source):
  • CUDA/cuDNN version: CUDA Version: 10.0
  • GPU model and memory: GeForce GTX 1080
  • Exact command to reproduce: python train.py --logtostderr --train_dir=...
Describe the problem

Running training twice with the same checkpoint as starting point results in different weights after the first step already. (The weights are the same after initialization from checkpoint 0).

Example:
Experiment A:

  • weights at checkpoint 0: 2230.3213
  • weights after the first step of traninig: 2230.3845

Experiment B:

  • weights at checkpoint 0: 2230.3213
  • weights after the first step of traninig: 2230.3768

Therefore i am suspecting that the training process (gpu) is having some non-determinism?

This results in incomparable results between many runs and parameter changes and makes scientific work barely possible.

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.