-
Notifications
You must be signed in to change notification settings - Fork 45.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Evaluation with model_main.py not using old checkpoints/don't evaluate choosen dataset #10710
Comments
Hi @Petros626, pipeline.config
Thank you! |
Hello @gadagashwini the suggested command is the same like mine, so the problem is the last saved checkpoint is not readed, TF will start a new training and the second thing is that i have to force in Your changing in the config file is to evaluate of COCO, which makes no sense in my case, because I have 3D-LiDAR data, so I evaluated on my training and test data. Here are my summaries to the behaviour:
|
@gadagashwini any tips? |
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 totrain.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
The text was updated successfully, but these errors were encountered: