[Bug] Colormap cannot be changed for the second volume in a VolumeViewport

[JoostJM]

Describe the Bug

When changing the colormap for the second volume, this always gets applied to the first volume. This is due to a bug in cornerstone extension commandsModule.ts, setViewportColormap. To set the colormap on a viewport, it requires the volumeId. Currently this is retrieved by viewport.getVolumeId(), which only returns the first volumeId.

It could be changed by adding a specifier, i.e. viewport.getVolumeId({ volumeId: <volumeId> }), but this requires the volumeId to update to be known or retrievable. In this function, the correct volume is identified by the DisplaySetInstanceUID, which is slightly different from the volumeId, and therefore cannot be directly used to get the correct volumeId.

Steps to Reproduce

1. Load the PET-data case in OHIF viewer.
2. Try to change the colormap on the PT volume in a fusion viewport. This applies the selected colormap to the CT volume (which is the first volume in the viewport)

The current behavior

Colormaps can only be changed for the first volume in a viewport.

The expected behavior

Selecting the second volume in the actionmenu should apply the chosen colormap to the second volume in the viewport.

OS

Linux 22.04.4 LTS

Node version

20.11.0

Browser

Chrome 122