inference.py: ValueError: Dimension 0 in both shapes must be equal, but are 1 and 2 for 'Assign_318'

[aurora95]

inference.py: ValueError: Dimension 0 in both shapes must be equal, but are 1 and 2 for 'Assign_318'

[DianaLi96]

@simonsayshi may be you can see the default classes in models.py ,change the default setting to what do you want, this may cause the model which last layer dimension is 21 in hdf5 file.it may be the reason of the problem.

[bgr33r]

I solved this. The Problem was with the model: it had 21 classes instead of 2.

[simonsayshi]

hi, how do you solve this issue?
I changed the classes in train.py from 21 to 5(my data has 5 classes) and the training works good but when I run evaluate.py(I also changed the nb_classes to 5) this issue occurs:

ValueError: Dimension 0 in both shapes must be equal, but are 1 and 5. Shapes are [1,1,4096,21] and [5,4096,1,1]. for 'Assign_30' (op: 'Assign') with input shapes: [1,1,4096,21], [5,4096,1,1].

this is really annoying since I matched the parameters for train and evaluate but this just keep showing, how did you solve it? thanks!

[simonsayshi]

@bgr33r

[bgr33r]

@simonsayshi I would recommend digging through your code and making sure that the variables relating to class number are set correctly. Also, you should make sure you're loading the correct model file (.hdf5). I "solved" the problem when I realized I had made a mistake with the number of classes denoted in the model (doh!).

[simonsayshi]

thanks for reply! but I still want make it clear.
I only changed the classe in train.py and nb_classes in evaluate.py for my dataset
when I use the original number, 21 classes, the train.py and evaluate.py works without any problems
but when I change it to any other number like 4 or 5(for both scripts), the issue occurs

I only have one model file which is generated by train.py so I don't think I loaded wrong model. So what did you do? did you just let the 'classes' in train.py and 'nb_class' in evaluate.py be the same number then everything works? this is what I did but the issue remains! :(