Google Code Exporter

``` The current version of dicompyler has some issues when running on Windows 7 / 2008 Server, where it crashes spontaneously. I think this has to do with the wxWidgets...

``` On a different machine, Windows 7 with more physical memory, the patient's files opened, but when I maximized the window, I got the following fatal error: Platform information: System:...

``` I think the error above(second post) is relating to a mouse action in the 2dview.py too soon after changing the drawing state. This same tuple/Point error used to occur,...

``` Hi Phil, lstrdean is correct regarding the mouse action in the 2D view. This was resolved in Issue 62. Regarding the first issue, I have never seen a memory...

``` Update: After I adjusted my mouse movement habits, as instructed, I was able to read the RT Dose (and other) files on my Windows 7 workstation. It has 8...

``` Might be able to quickly fix the memory error if the Numpy arrays are split into multiple ones, any way to prevent a massive element wise operation. It could...

``` Hi Jakob, Thanks for the suggestions. The features you mentioned are features that I have considered implementing before, but I haven't had any time to work on them. I...

``` The next version will support Rx Dose that is derived from the fractionation information within an RT Plan file. So far, this has covered all of the cases that...

``` Since r57d9155cc415, dicompyler does not use Slice Location tag at all, but rather uses Image Position Patient. I have not personally seen this issue since then with any datasets...

``` I think the DVH architecture of dicompyler needs to be refactored to support arbitrary bin sizes. Currently it expects (either by source data or by conversion) that the bin...