Page MenuHomePhabricator

Max bound error when loading Dynamic DICOM images
Closed, ResolvedPublic

Description

In some cases loading dynamic DICOM images can cause the following error (see example below) and fail to load the data:

Error encountered when loading DICOM series:/home/ubuntu/jenkins-agent/MITK/Snapshots/src/MITK/Modules/Core/src/DataManagement/mitkArbitraryTimeGeometry.cpp:276:
Cannot append geometry to time geometry. Time bound conflict. Maximum time point (1000) is smaller than minimum time point (380224).
Aborted (core dumped)

In the cases found so far the reason was that the first few time steps hat the same acqu time/date and only differ in trigger time, thus bounds and duration where computed by trigger time. Later time steps had a new acq time (for what ever reason) and also the right trigger time. But the later was ignored as the acq time has changed -> leading to invalid bounds.

Solution: As soon as trigger time is used to compute bounds, all succeding time steps should also use the trigger time, no matter if the acq has changed.

  • Please describe the bug or feature request as long as necessary but as short as possible.
  • What information is necessary to reproduce the bug? For example, what version of MITK do you use, what is your operating system?
  • Unless you are sure about the priority, Needs Triage is perfectly fine.
  • As an external reporter, please do not change Needs Triage. Otherwise the task may drown in the daily task noise, while the list of Needs Triage tasks is guaranteed to be reviewed regularly.
  • Do not assign the task to someone else. Instead, consider adding other users as subscribers or explicitly mention them with the @ syntax.
  • If you have a GitHub pull request, please add the Pull Request tag below.

Revisions and Commits

rMITK MITK
Restricted Differential Revision
Restricted Differential Revision
Restricted Differential Revision