matterport / matterport/Mask_RCNN

[Issue] Incompatible shapes during training of own dataset

Open
#331 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
25.6k
Forks
11.6k
PR merge metrics
No merged PRs in 30d

Description

Hello again,

I successfully managed to use my dataset but the problem apparently is with the shapes inbetween layers...

I get the following error:

InvalidArgumentError (see above for traceback): Incompatible shapes: [8,28,28] vs. [8,512,512]
[[Node: mrcnn_mask_loss/logistic_loss/mul = Mul[T=DT_FLOAT, _device="/job:localhost/replica:0/task:0/device:CPU:0"](mrcnn_mask_loss/Log, mrcnn_mask_loss/Gather_1)]]

I did change the batch size to see if there were any changes, and the shapes switch to [8,28,28] to [6,28,28] when I change the batch size from 16 to 8.

Here are screens of the configuration and the error (partly):

![Error](https://user-images.githubusercontent.com/12952763/37407595-58574a5a-279a-11e8-9365-64dc40d2b3fc.PNG)
![Config](https://user-images.githubusercontent.com/12952763/37407596-588d375a-279a-11e8-964d-413803a0bc6d.PNG)

I resized the images to be (512,512) as well. The problem seems to come from the "mul" gradient... But that's all I can even understand...

Thanks for your help.

Contributor guide

No contributing guide indexed for this repository

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.

Research direction

No source file, test, or entry point is named. Start by reproducing training on the reported custom dataset with the shown configuration, then trace the mask-loss inputs associated with mrcnn_mask_loss/logistic_loss/mul. Done means identifying the source of the incompatible [8,28,28] and [8,512,512] shapes and confirming training proceeds with matching mask dimensions.

Written by the indexing model from the issue text.

Assessment

Tech stack
keras, python, tensorflow
Domain
computer-vision, machine-learning
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.