PixelBuffer resolution levels in unexpected order

[mtbc]

It's not easy to figure out from the PixelBuffer Javadoc how to use instances, e.g., what should be expected from the byte-swapping that is mentioned, which way around the data will end up. More critically, getResolutionDescriptions suggests that the indices of the return value have,

the resolution level matching the index of the outer index

but in my experiments with instances of BfPixelBuffer and BfPyramidPixelBuffer they are in the opposite order. For example, with 77917.svs the last item of the description list is [1024, 482] which is the resolution I get from setResolution(0).