tensorflow / tensorflow/models

ValueError: faster_rcnn_inception_v2 is not supported / ValueError: numpy.ndarray size changed, may indicate binary incompatibility. Expected 88 from C header, got 80 from PyObject

Open
#10,135 1 comment 0 reactions 3 assignees View on GitHub

@pkulzc is already working on this.

Since Aug 4, 2021.

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

Description

Hi, I'm trying to run this line of code in a virtual environment in the linux terminal:
python3 model_main.py --logtostderr --model_dir=training/ --pipeline_config_path=training/faster_rcnn_inception_v2_pets.config
as per instructions from this tutorial here
but I get this error:

    raise ValueError('{} is not supported. See `model_builder.py` for features '
ValueError: faster_rcnn_inception_v2 is not supported. See `model_builder.py` 
for features extractors compatible with different versions of Tensorflow

I then found out that it is because I am attempting to train a tensorflow 1 model using tensorflow 2, so I tried to uninstall tensorflow 2 and re-install tensorflow 2 but got this error message:

ERROR: Could not find a version that satisfies the requirement tensorflow==1.15 (from versions: 2.2.0rc1, 
2.2.0rc2, 2.2.0rc3, 2.2.0rc4, 2.2.0, 2.2.1, 2.2.2, 2.2.3, 2.3.0rc0, 2.3.0rc1, 2.3.0rc2, 2.3.0, 2.3.1, 2.3.2, 2.3.3, 
2.4.0rc0, 2.4.0rc1, 2.4.0rc2, 2.4.0rc3, 2.4.0rc4, 2.4.0, 2.4.1, 2.4.2, 2.5.0rc0, 2.5.0rc1, 2.5.0rc2, 2.5.0rc3, 2.5.0, 
2.6.0rc0, 2.6.0rc1)
ERROR: No matching distribution found for tensorflow==1.15

I also get the is error message as well:
ValueError: numpy.ndarray size changed, may indicate binary incompatibility. Expected 88 from C header, got 80 from PyObject
I complete every step in the tutorial with success but when I try to train the model I get a bunch of errors. I resolve one and get another.

Please help me with this issue.

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.