-
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
obj detection training with faster_rcnn_inception_v2_coco Argument must be a dense tensor: range(0, 3) - got shape [3], but wanted []. #3948
Comments
I just uninstalled tensorflow 1.7.0 and installed 1.5.0, then rerun the protoc compilation and setup.py install of the tensorflow models ssd runs fine except for #3922 but it seems to train decently enough |
I'm actually having the same issue here, |
@elkalash the depreciate warning is not the issue here. |
Hi. Could you modify |
Got the same issue.
Found the solution : #3705 (comment) |
That does indeed seem to be the case. Thanks a lot for finding and linking that. |
I got the same problem in win10, how to solve it? |
@yafengwa |
I got the same error when tried to train faster_rcnn_resnet101 coco from model zoo. |
System information
TensorFlowModels\research\object_detection
No, though PycocoAPI from here
The problem also appeared without those modifications I made:
Windows 7 x64
Installed with pip
1.7.0
CPU version
CPU version
python train.py --pipeline_config_path="PATH_TO_MODELS/Models/faster_rcnn_inception_v2_coco/pipeline.config" --train_dir="PATH_TO_MODELS/Models/faster_rcnn_inception_v2_coco/train"
Describe the problem
trying to run the command above with tfrecords in the form of
and the faster_rcnn_inception_v2_coco model from 2018_01_28 creates the following errors:
Source code / logs
Note: I've been using the detection api last when tensorflow version 1.4 was current. since updating i couldn't run ssd_mobilenet_v1 anymore, since the pretrained model checkpoint seems to missmatch the configuration. so I decided to try faster_rcnn and get this issue instead.
my pipeline config:
PATH_TO_PROJECT of course is not really written there, but rather the path would be giving away what I'm working on, and I signed an NDA, so I replaced it here.
The text was updated successfully, but these errors were encountered: