Page MenuHomePhabricator
Create Task
Maniphest T19999

DICOM CGet and CMove don't work correctly
Closed, WontfixPublic
Actions

Description

Version: Release 2016-03 (Windows)

Tested MITK DICOM Editor with a Osirix-Server.

  1. CGet-Mode does not work at all
  2. CMove-Mode does work sometimes, sometimes it does not. In the later case there is traffic, but the data does not end up in the local storage. The reason for this is unclear. Sometimes closing the editor or just randomly selecting and deselecting make it work. One first assumption (must be verified) is that ist depends on wether the patient is selected directly (works) or just series are selected (does not work).
  3. If a patient is selected and the data is recieved (CMove) not all series end up in the local storage. This behaviour seems to be deterministic (so the series are always missing). If the problematic series is pushed to MITK by the server, everything works fine. The current assumption is that the reason could be, when the (series) description containes special characters. (At least all missing series had an "*" in their description.

Related Objects

Event Timeline

floca created this task.Sep 20 2016, 5:57 PM
floca triaged this task as Normal priority.Sep 20 2016, 6:11 PM
floca updated the task description. (Show Details)
floca added projects: Restricted Project, Restricted Project.
floca mentioned this in T19597: Dicom QR C-Move request fails in some cases.Oct 4 2016, 12:10 AM
floca raised the priority of this task from Normal to High.Oct 4 2016, 12:12 AM
nolden renamed this task from DICOM CGet and CMove work not correctly to DICOM CGet and CMove does not work correctly.Nov 4 2016, 12:11 PM
nolden renamed this task from DICOM CGet and CMove does not work correctly to DICOM CGet and CMove don't work correctly.
floca added subscribers: reicht, gaoh.Jan 15 2019, 3:52 PM

We should verify if the problem still exists with Osirix. DICOM Q/R with wDB was checked 2-3 month ago and was working correctly.

reicht added a comment.Feb 8 2019, 6:07 PM

I can setup a Horos instance (=OsiriX fork since free edition of osirix is limited and not userfriendly anymore) if needed. This can be done in the science network to avoid any firewall issues when trying to QR from a SIDT computer.

reicht added a comment.Feb 13 2019, 5:31 PM

OsiriX / Horos instance is online:

IP: 193.174.49.138
AET: e010-pc61
Port: 11112

All stored data is pseudonymised.

floca lowered the priority of this task from High to Low.Feb 13 2019, 5:45 PM

@reicht: Thanks
@gaoh : Could you (not of high priority; so within the next month, or at a community day) check if the problem still exists with a actual installer. If you need an installer with DICOM editor, i can provide one.

gaoh added a comment.Feb 13 2019, 5:52 PM

yes I will try, I already tried Q/R with the current installer and the wdb and it worked.

gaoh added a comment.Feb 15 2019, 12:18 PM

Point 1 and 2 are working.
With point 3: not all the series are downloaded: I retrieved all 5 series of a patient, but only got 2 series. Separately retrieving of each series was fine.

floca added a comment.Feb 15 2019, 1:18 PM

OK, then there is still an error with test 3.

As you have the setup currently running, could you try to get a bit more information about the error/why it is happening?

e.g.

  • Infos in the log file that hints to the problem
  • Is the problem always
  • Is always the same missing

...

gaoh added a comment.Mar 15 2019, 12:30 PM

The log entries don't tell me a lot, basically I thing for every file it writes: ERROR: setting value to 0
Just in the end, before the termination the log entries change to:

ERROR|Fri Mar 1 10:58:48 2019 ||H:\MITK\Modules\AppUtil\src\mitkBaseApplication.cpp(6a)|mitk::outputQtMessage|2b8c|mbilog|setting value to 2
ERROR|Fri Mar 1 10:58:49 2019 ||H:\MITK\Modules\AppUtil\src\mitkBaseApplication.cpp(6a)|mitk::outputQtMessage|2b8c|mbilog|setting value to 3
ERROR|Fri Mar 1 10:58:50 2019 ||H:\MITK\Modules\AppUtil\src\mitkBaseApplication.cpp(6a)|mitk::outputQtMessage|2b8c|mbilog|setting value to 100
ERROR|Fri Mar 1 10:58:51 2019 ||H:\MITK\Modules\AppUtil\src\mitkBaseApplication.cpp(6a)|mitk::outputQtMessage|2b8c|mbilog|setting value to 0
ERROR|Fri Mar 1 10:58:52 2019 ||H:\MITK\Modules\AppUtil\src\mitkBaseApplication.cpp(6a)|mitk::outputQtMessage|2b8c|mbilog|setting value to 0
ERROR|Fri Mar 1 10:58:53 2019 ||H:\MITK\Modules\AppUtil\src\mitkBaseApplication.cpp(6a)|mitk::outputQtMessage|2b8c|mbilog|setting value to 1
ERROR|Fri Mar 1 10:58:54 2019 ||H:\MITK\Modules\AppUtil\src\mitkBaseApplication.cpp(6a)|mitk::outputQtMessage|2b8c|mbilog|setting value to 2
ERROR|Fri Mar 1 10:58:55 2019 ||H:\MITK\Modules\AppUtil\src\mitkBaseApplication.cpp(6a)|mitk::outputQtMessage|2b8c|mbilog|No responses received at all! (at least one empty response always expected)
ERROR|Fri Mar 1 10:58:57 2019 ||H:\MITK\Modules\AppUtil\src\mitkBaseApplication.cpp(6a)|mitk::outputQtMessage|2b8c|mbilog|setting value to 0
ERROR|Fri Mar 1 10:58:58 2019 ||H:\MITK\Modules\AppUtil\src\mitkBaseApplication.cpp(6a)|mitk::outputQtMessage|2b8c|mbilog|setting value to 0
ERROR|Fri Mar 1 10:58:59 2019 ||H:\MITK\Modules\AppUtil\src\mitkBaseApplication.cpp(6a)|mitk::outputQtMessage|2b8c|mbilog|setting value to 1
ERROR|Fri Mar 1 10:59:00 2019 ||H:\MITK\Modules\AppUtil\src\mitkBaseApplication.cpp(6a)|mitk::outputQtMessage|2b8c|mbilog|setting value to 2
ERROR|Fri Mar 1 10:59:01 2019 ||H:\MITK\Modules\AppUtil\src\mitkBaseApplication.cpp(6a)|mitk::outputQtMessage|2b8c|mbilog|No responses received at all! (at least one empty response always expected)
ERROR|Fri Mar 1 10:59:02 2019 ||H:\MITK\Modules\AppUtil\src\mitkBaseApplication.cpp(6a)|mitk::outputQtMessage|2b8c|mbilog|setting value to 0
ERROR|Fri Mar 1 10:59:03 2019 ||H:\MITK\Modules\AppUtil\src\mitkBaseApplication.cpp(6a)|mitk::outputQtMessage|2b8c|mbilog|setting value to 0
ERROR|Fri Mar 1 10:59:04 2019 ||H:\MITK\Modules\AppUtil\src\mitkBaseApplication.cpp(6a)|mitk::outputQtMessage|2b8c|mbilog|setting value to 1
ERROR|Fri Mar 1 10:59:05 2019 ||H:\MITK\Modules\AppUtil\src\mitkBaseApplication.cpp(6a)|mitk::outputQtMessage|2b8c|mbilog|setting value to 2
ERROR|Fri Mar 1 10:59:06 2019 ||H:\MITK\Modules\AppUtil\src\mitkBaseApplication.cpp(6a)|mitk::outputQtMessage|2b8c|mbilog|No responses received at all! (at least one empty response always expected)
ERROR|Fri Mar 1 10:59:08 2019 ||H:\MITK\Modules\AppUtil\src\mitkBaseApplication.cpp(6a)|mitk::outputQtMessage|2b8c|mbilog|setting value to 0
ERROR|Fri Mar 1 10:59:09 2019 ||H:\MITK\Modules\AppUtil\src\mitkBaseApplication.cpp(6a)|mitk::outputQtMessage|2b8c|mbilog|setting value to 0
ERROR|Fri Mar 1 10:59:10 2019 ||H:\MITK\Modules\AppUtil\src\mitkBaseApplication.cpp(6a)|mitk::outputQtMessage|2b8c|mbilog|setting value to 1
ERROR|Fri Mar 1 10:59:11 2019 ||H:\MITK\Modules\AppUtil\src\mitkBaseApplication.cpp(6a)|mitk::outputQtMessage|2b8c|mbilog|setting value to 2
ERROR|Fri Mar 1 10:59:12 2019 ||H:\MITK\Modules\AppUtil\src\mitkBaseApplication.cpp(6a)|mitk::outputQtMessage|2b8c|mbilog|No responses received at all! (at least one empty response always expected)

When selecting all the studies, the first study (with 42 Series) and 9 series off the second study are downloaded. I tried it twice, both times 950 MB and 2439 files have been downloaded.
When unselecting the first 2 studies 2100 Files and 693 MB are downloaded before it stops (also tried it twice, and for each time exactly the same number of files have been retrieved). The log-files have always the same errors before the termination.
When only downloading a study at a time, there are no problems.

@reicht: I could need some patients with less images, but the same number of studies and series, to see if the problem is more a size/number of images problem, or a studie /series number matter.
This would also speed-up the testing. The download is not the fastest .. it take about 1,5h to download 1GB

kislinsk closed this task as Wontfix.Oct 14 2021, 11:38 AM
kislinsk added a subscriber: kislinsk.

Hi there! 🙂

This task was auto-closed according to our Task Lifecycle Management.
Please follow this link for more information and don't forget that you are encouraged to reasonable re-open tasks to revive them. 🚑

Best wishes,
The MITK devs

MITK · MIC · IMSY · DKFZ