Structures are not listed

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Open a patient under Linux (with proper CT, STRUCT, DOSE and PLAN 
information).
2. The list of structures is empty.

What is the expected output? What do you see instead?
The expected output is given in the attached file "DicompylerWindows.png". This 
is the result under Windows. The structures are properly displayed. The actual 
output is given in the attached file "DicompylerLinux.png". There is no 
structure.

What version of the product are you using? On what operating system?
I am under Ubuntu 11.10. The problem both occurs in the cutting edge revision 
of the repository and in version 0.4.1-1.

Please provide any additional information below.
I also notice that the "Loading Patient Data" dialog box does not appear under 
Linux.

Original issue reported on code.google.com by s.jodo...@gmail.com on 5 Mar 2013 at 4:07

Attachments:

• DicompylerLinux.png
• DicompylerWindows.png

[GoogleCodeExporter]

Update: This problem does not occur on Ubuntu 12.10 with the same data.

Original comment by s.jodo...@gmail.com on 5 Mar 2013 at 6:45

[GoogleCodeExporter]

Update: This problem can also occur on a fresh Ubuntu 12.10 install (in a 
virtual machine). I guess this is a versionning problem for some toolkit used 
by Dicompyler. I also notice that this is not just a display problem: No 
structure exists when I examine the variables.

Original comment by s.jodo...@gmail.com on 6 Mar 2013 at 10:06

[GoogleCodeExporter]

Thanks for reporting this. I currently don't have access to Ubuntu 12.10, but 
dicompyler seems to work well in Ubuntu 10.10.

I wonder if this is a pydicom issue, as dicompyler will only work with pydicom 
0.9.6. If 12.10 comes with 0.9.7 or is installed via pip/easy_install it may 
not work. I assume pydicom 0.9.8 may work, but I have not tested it.

It is also possible that it is a wxPython issue. Only wxPython 2.8.10.1 has 
been tested and higher versions may break it.

Original comment by bastula on 7 Mar 2013 at 4:11

[GoogleCodeExporter]

Thanks for your answer. The version of pydicom was indeed the culprit: I had 
installed the latest version of pydicom (0.9.8, presumably through a "sudo 
easy_install pydicom" or so). After uninstalling pydicom 0.9.8 and switching to 
0.9.4-1 (the default version of Ubuntu 11.10), everything worked properly.

Just a few hints that would be interesting to mention prominently on Dicom 
homepage for Linux/Ubuntu (notably on the wiki page UbuntuInstall):

 * The currently installed version of pydicom can be obtained through 2 equivalent commands:

`# pip search pydicom`

`# python -c "import dicom; print dicom.__version__"`

 * To force pydicom 0.9.7 to be installed, type:

`# sudo pip install pydicom==0.9.7`

Finally, an additional suggestion: It would be really great to have a warning 
when the version of pydicom is not supported when starting Dicompyler. As 
written above, it should be quite easily achieved through a test on the 
variable `dicom.__version__`.

Anyway, thanks for your great work on Dicompyler!

Regards,
Sébastien-

Original comment by s.jodo...@gmail.com on 7 Mar 2013 at 8:29

[GoogleCodeExporter]

Good to hear that you got it figured out. I have used those commands in the 
past to install specific versions of packages.

I will modify the UbuntuInstall guide to reference your suggestions.

Thanks!

Original comment by bastula on 14 Mar 2013 at 2:02

• Changed state: Done

[GoogleCodeExporter]

I encountered this same problem, and also found the pydicom version to the
 the problem.  The problem that the newer version complained about for
 me pertained to the use of some depreciated dicom lables.  Things like
 using "PatientsSex" instead of "PatientSex".

Original comment by amvent...@gmail.com on 4 Apr 2013 at 2:57