-
Notifications
You must be signed in to change notification settings - Fork 26
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
input dimension #14
Comments
Shape must be (#images, width, height, #slices, 1). Last 1 is needed. |
I have followed the recommended input shape and getting error of ValueError: axes don't match array or ValueError: Input 0 of layer "model_3" is incompatible with the layer: expected shape=(None, 96, 224, 224, 35), found shape=(1, 224, 224, 35, 1). |
You put input shape: Do you have 35 channels? If you have 1 channel use:
|
Yes, that was my thought, then I got this error: ValueError: Input 0 of layer "zero_padding3d" is incompatible with the layer: expected ndim=5, found ndim=6. Full shape received: (None, 96, 224, 224, 35, 1) |
Shape must be: |
96 is the number of images. |
You don't need to specify it. |
Thanks for the reply. Now with Linknet and densenet121 I have this error: ValueError: Inputs have incompatible shapes. Received shapes (56, 56, 8, 128) and (56, 56, 9, 128) and with UNet and densenet121 , I have the following error: ValueError: A |
Yes. Each dimension must be divisible on 32. I think I should add warning message for this case. |
I need to think how to make it work for any value of dimensions. |
Hi, |
Can you provide exact error message? |
Yes,
|
Try encoder_weights=None |
I tried encoder_weights=None, and it works. |
Try to do this:
|
Unfortunately same error |
my input data has the shape of (118, 224, 224, 35), 118 3D nii images, width: 224, height: 224 and depth (#of slices) 35. My question is what would be the correct order of input shape? is the order of (#images, width, height, #slices) correct? Some examples use the shape of (#images, width, height, #slices, 1). Should I set the last dimension to 1 as channel dimension?
The text was updated successfully, but these errors were encountered: