> Not quite. These problems with singleton dimensions appearing in > unexpected places often occur when working with high-dimensional arrays. > I'm unfortunately short on real-world examples I can readily share, but > I've definitely run into this before: a well-intentioned squeeze() ends up > collapsing something that started as an (n x m x p x 1) array which you > expected to become a (n x m x p) array into an (n x p) array because m > happened to be 1. Now you go to slice the resulting array and things aren't > where you thought you'd find them, and stuff breaks in confusing ways. >
Yeah, I can see it better now. Thanks!
