[Bug] setDefaultVolumeVOI bug

[aodong8808]

Describe the Bug

getVOIFromMetadata logic error in setDefaultVolumeVOI

Steps to Reproduce

1、 const volume = await volumeLoader.createAndCacheVolume(ctVolumeId, { imageIds: [...imageIds] });
2、options.imageIds of cornerstoneStreamingImageVolumeLoader is in positive sequence,

const [middleImageIndex, lastImageIndex] = [ Math.floor(options.imageIds.length / 2), 
options.imageIds.length - 1, ];

the obtained middleImageIndex is 29, and the imageId is 'wadouri:http://~1.2.840.113619 .2.472.3.40120842.710.1685265533.1.30.dcm'
Why is the imageIds obtained in
const { imageIds, metadata } = imageVolume;
in getVOIFromMetadata in reverse order, resulting in

const imageIdIndex = Math.floor(imageIds.length / 2);
const imageId = imageIds[imageIdIndex];

The imageId obtained is 'wadouri:http://~1.2.840.113619.2.472.3.40120842.710.1685265533.1.29.dcm',
the image has not been downloaded yet,
const voiLutModule = metaData.get('voiLutModule', imageId);
voiLutModule is undefined, the voi obtained by getVOIFromMiddleSliceMinMax is incorrect and very different from the image itself. Why is the order of imageIds reversed?

The current behavior

The obtained windowWidth and windowCenter are incorrect.

The expected behavior

getVOIFromMetadata returns the correct voi

OS

windows11

Node version

16.14.0

Browser

chrome