:smile: I hit an issue when testing where if the uncollapsed cube had been transposed, the dimension mapping can still be calculated and the shape modified (as the total size of the array is unchanged), but it messes up your data resulting in a silent failure. For example:
```
cube.shape = (2, 3, 4)
collapsed_cube.shape = (4, 3)
```
```new_shape``` would be ```(1, 3, 4)```, but by reshaping the data like this it gets jumbled up as rows wrap around. I coded up how to detect this (```new_order``` code), and was going to simply raise an exception, but having determined it has occurred it's easy to fix, thereby removing the constraint that the dimensions in the two cubes have to be in the same order.