all the input arrays must have same number of dimensions
See original GitHub issue🐛 Bug
To Reproduce
Steps to reproduce the behavior:
when i use the notebook from https://github.com/qubvel/segmentation_models/blob/master/examples/multiclass segmentation (camvid).ipynb, with Resize transform turn on, raises the above error.
Expected behavior
Environment
- Albumentations version (0.3.3):
- Python version (3.6):
- OS (Linux):
- How you installed albumentations (
pip
): - Any other relevant information: segmentation models version(1.0.0)
Additional context
Issue Analytics
- State:
- Created 4 years ago
- Comments:9
Top Results From Across the Web
all the input arrays must have same number of dimensions ...
If I start with a 3x4 array, and concatenate a 3x1 array, with axis 1, I get a 3x5 array: In [911]: x...
Read more >How to Fix: All input arrays must have same number of ...
This error can be fixed by making the dimensions of both the arrays the same if we want to use concatenate function only....
Read more >All input arrays must have same number of dimensions
This tutorial explains how to fix the following error in NumPy: ValueError: all the input arrays must have same number of dimensions.
Read more >the input arrays must have same number of dimensions, but ...
I'm in page 125 and the code tries to concatenate an np array using some kinda-hardcore tuples using some keras data batches. My...
Read more >got error all the input arrays must have same number ... - GitHub
got error all the input arrays must have same number of dimensions, but the array at index 0 has 2 dimension(s) and the...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I’m pretty sure the fix here is:
Currently:
Becomes:
Fixed #364