Aeskulap images not seen

Hello,

we tested aeskulap in Debian and realised that the problem of version 0.2.2b1-2 is that the version of the libraries on which it depends are not correctly specified. It works on freshly installed Debian Lenny systems, so it may probably work with Ubuntu Intrepid.

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=492842

Have a nice day,

--
Charles Plessy
Debian Med packaging team
http://www.debian.org/devel/debian-med
Tsurumi, Kanagawa, Japan

This bug report does not mention that aeskulap also fails to recognize DICOM files using the file browser under "File-Open". So then bug #267554 is not, strictly speaking, a duplicate of this bug.

> It works on freshly installed Debian Lenny systems,
> so it may probably work with Ubuntu Intrepid.

My understanding is that Hardy will provide Long Term Support, so leaving aeskulap "broken" in Hardy does not seem like an appropriate response.

Got my MRI scans, installed and fired aeskulap up on my ubuntu hardy box to view them, and saw nothing but a blank screens. :( Had to use my wife's windows box.

+1 with James to have this fixed on hardy.

I have cd's of ct scans after various amounts of chemotheraphy. I need to compare progress of shrinking my tumors. It is very disappointing that this long term release is passed off by telling me that I can only take care of my life properly if I move to Debian Lenny.

Hello,

sorry for the misunderstanding: I did not want to suggest anybody to move to Lenny. The purpose of my message was to inform Ubuntu developers that the binary package that is in Hardy works unmodified on Debian Lenny, because it suggests that the cause for the black screen is probably to be looked for in the interaction between aeskulap and the libraries it depends.

I would like to emphasise again that I am not a Ubuntu developer. I monitor the bugs of this package because I belong to the team that produced it upstream in Debian, and I took the freedom to mark #267554 as I think that it has the same cause. It is indeed more informational and next time I do something like this I will include a summary :)

I hope this clarifies. For the moment no Ubuntu developer expressed himself on this bug, so there is definitely nothing that suggests that it can not be fixed in Hardy. How about contacting the Ubuntu MOTU science team?

Have a nice day,

Aeskulap does not work on intrepid either :(

It's sees that the directory access is still bugged. However, I found an easy fix until they bring the Beta fix out. make sure you have freej & imagej installed. then open the images directory in nautilus & right click, open with, use specific command- aeskulap . This will allow you to view each individually. Please keep in mind that I have only tested this with McKee & Banner images. Tested Ubuntu Intrepid AMD64 & i386. Jay

I can confirm this bug in aeskulap 0.2.2-beta1 It does not open any CT files from GE Medical Systems. It doesn't recognize DICOMDIR files properly. Workaround presented by jaypmcwilliams doesn't help. I see only blank imagec.

xmedcon - recognizes DICOM files but as no DICOMDIR support.

The bug is still present in Jaunty alpha 5

Architecture: amd64
Version: 0.2.2b1-2
Kernel: 2.6.28-8-generic #28-Ubuntu SMP x86_64 GNU/Linux

The package has been updated (minor changes) on Debian (0.2.2b1-4). I am not sure if it will change something, but maybe you can ask the MOTU to sync the packages?

Have a nice day,

--
Charles

Hi boys, (and girls)

I've just tested the aeskulap package yesterday (0.2.2b1-1), it work fine in a Ubuntu 8.04 LTS x86-64 up to date, kernel 2.6.24-24-generic.

.... and I've try to rerun it now before to post .... sorry now it send a seg-fault ....

well in fact I'm working with DICOM dcmtk compilation and linking, so the bug is probably with dependencies between dcmtk and aeskulap packages.

best regards,

Samuel

0.2.2b1-4 is in the Karmic repositories. I just tested the Karmic version in my Jaunty installation (after updating gcc-4.4-base and libstdc++6 to the Karmic versions, to satisfy its dependencies). It still doesn't work. Can one of the developers please investigate why this works in Debian but not in Ubuntu?

(When you open a dicomdir, it seems to open it, and lets you list all of the series that comprise it in "Study Manager" view, but it doesn't let you open any of the series or see their images. When you try to open individual dicom files via file->open, it doesn't see them until you change the file type filter from "DICOM Files" to "Any files." Then it lets you see and open them. So you can open individual files, but the program is kind of useless since its ability to open dicomdirs and see the images that comprise them is broken.)

Since Charles suggested the problem might be incorrectly specified dependencies, I compared the dependencies of the newest version of this program (0.2.2b1-4) in Debian (Squeeze) and Ubuntu (Karmic), for the platforms supported by Ubuntu (i386 and amd64). I've attached a list of the differences I found.

I made sure my amd64 system satisfied both the Debian and Ubuntu dependencies in all cases. (I had to update libxcb-render-util0 to the Karmic version to meet the Debian dependency.) But it still won't run on my system.

So I'm thinking it's not just a matter of Ubuntu specifying less dependencies (or depending on insufficiently new versions of libraries) compared to Debian.

Oops, nevermind. The problem is much less severe than I thought. DICOMDIR files (and the images they contain) can be opened (on either the Jaunty or Karmic versions). You just have to load them through the following two-step process.

1) File menu -> DicomDir -> select the DICOMDIR, and click "Open." This should make a new folder (representing the contents of the dicomdir) appear in "Study Manger" view.
2) Double-click on this folder in "Study Manager" view to load in all of the images contained in the dicomdir. (You have to double-click on the folder, not any of the enclosed series.)

I just didn't realize the second step was necessary. My bad.

There is still a slight bug here, in that when you try to open individual DICOM files through File->Open, it doesn't see any dicom files unless you change the file type selector from "DICOM files" to "Any files." But it will open them once you do that. So not a critical bug, but it would be nice to have it fixed at some point.

It just don't work. Nothing about Aeskulap work in Jaunty!

@David S.

when I do step 1, which is just the default way (i can't see the differences!) i get

"No study or bad DICOMDIR"

that is. Is there someone to which this Aeskulap works in Jaunty?

I have Ubuntu 9.04 64-bit installed. When I installed dcmtk:

sudo apt-get install dcmtk

Aeskulap worked!

Good news !

The 0.2.2b1-4 package in karmic depends on dcmtk, so the problem will be automatically solved at the next Ubuntu release.

I confirm all of the above on Hardy:

$ sudo aptitude install aeskulap

= Fails as noted above: error on opening DICOMDIR, black screen when manually viewing files, etc.

WORK-AROUND for Hardy, as per Samuel and GT Ducati above (thanks!):

$ sudo aptitude install aeskulap dcmtk

= Works as expected (note that you do have to double-click on the folder icon in the study tab for it to do anything useful. But that's a UI bug, not this one.)

So it looks like a trivial fix for Hardy, at least: update the package to depend on dcmtk. Since Hardy is LTS and since without this fix the package is useless (at least for newbies), I'd like to strongly urge someone to take the 5 minutes and tweak the Ubuntu Hardy (and newer) packages!

This is fixed in Lucid and Maverick