Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug] Dicom enhanced split in multiple files only load the first instance. #4388

Open
ThomasLempereur opened this issue Sep 25, 2024 · 0 comments
Labels
Awaiting Reproduction Can we reproduce the reported bug?

Comments

@ThomasLempereur
Copy link

Describe the Bug

Hello !
I'm currently trying to view a CT multiframe enhanced series with the version 3.7.0. But it only load the frames of the first instance.
My series contains 1344 frames split in 8 files/instances.
For each instance I have as metadata (that sounds important in this case):

  • the NumberOfFrames (with a value of 168 because it's the number of frame by multiframe image)
  • the InstanceNumber (1 to 8 depending of the instance)

Do I miss something ? A special tag that needs to be set / mandatory in the qido or metadata call ? or is it not supported ?

Thanks in advance !

Thomas :)

Steps to Reproduce

It happens like this while I'm calling my series:

  1. /api/dicom-web/studies/1.2.3/series?SeriesInstanceUID=4.5.6 -> [{SERIES_METADATA}]
  2. /api/dicom-web/studies/1.2.3/series/4.5.6/metadata -> [8 elements, each instance metadata]
  3. frame calls only for the first instance for each frames. /1 ... /168
  4. and then nothing, no error, no more call

The current behavior

the viewer only asks for the frames of the first instance despite the 8 instances metadata retrieved.

The expected behavior

I expected 8 * 168 calls of frames. (and reproduced with a smaller one).

OS

Windows 11

Node version

20.11.1

Browser

Brave 1.70.117 chromium: 129.0.6668.59

@ThomasLempereur ThomasLempereur added the Awaiting Reproduction Can we reproduce the reported bug? label Sep 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Awaiting Reproduction Can we reproduce the reported bug?
Projects
None yet
Development

No branches or pull requests

1 participant