tensorflow / tensorflow/models
Evaluation with model_main.py not using old checkpoints/don't evaluate choosen dataset
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 77.7k
- Forks
- 44.8k
- PR merge metrics
- No merged PRs in 30d
Description
Hello,
I want to evaluate my training and test data and I found several approaches do to that with eval.py and model_main.py.
Now my problem is, that the script begins to train from the beginning and evaluates the test data, even if the the flag --eval_training_data is True. One guess is to change the eval_input_reader in my config file to train.record, but not sure.
Could please someone help me with this, don't want to start from the beginning, if i already have checkpoints...
set CONFIG_FILE=C:\Users\petros.katsoulakos\models2\models-master\research\object_detection\training\ssd_mobilenet_v2_quantized_300x300_coco_custom_aspect_ratios.config
set OUTPUT_DIR=C:\Users\petros.katsoulakos\models2\models-master\research\object_detection\tensorboard_outputs\after_training\eval_train_data
set CHECKPOINT_PATH= C:\Users\petros.katsoulakos\models2\models-master\research\object_detection\training\model.ckpt-200000
python model_main.py --pipeline_config_path=%CONFIG_FILE% --model_dir=%OUTPUT_DIR% --eval_training_data=True --checkpoint_dir=%CHECKPOINT_PATH% --run_once=True
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.
Research direction
Start with model_main.py and eval.py, then inspect how --checkpoint_dir, --eval_training_data, and eval_input_reader from the pipeline config are used. Reproduce the command with the supplied checkpoint and configuration; done means evaluation uses the requested existing checkpoint and selected dataset without beginning training.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, tensorflow
- Domain
- machine-learning
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100