Google Code Exporter

Results 21344 comments of Google Code Exporter

``` Is anyone actually interested in this bug report? ``` Original comment by `[email protected]` on 16 Feb 2012 at 2:24

``` Of course, but you have to give us a little time to respond, it's a for-the-love-of-the-matter effort. When you get that error, it means that the the IPP (image...

``` (in short: there is something going on with your series. sometimes the first overview image is the culprit.) ``` Original comment by `cpbotha` on 17 Feb 2012 at 9:51

``` Good to know that. I fully understand your "for the love of the matter" attitude, because I was a software developer myself. It's cool that you enjoy it! I...

``` Hi there! DeVIDE tries to stack the images according to the Image Position Patient (IPP) as well as the Image Orientation Patient (IOP) vector, as recommended by DICOM gurus...

``` It's been a while, sorry guys! Anyway, the only two things that are changing in metadata of the images (in one series) are DataOrigin key and ImageNumber. So I...

``` The IPP ond IOP are stored in the normal DICOM tags. It's possible that the DICOMBrowser doesn't show them in the metadata window due to limitations in the VTK...

``` Hello all, I found devide today, when trying to figure out why InVesalius 3.0 beta 3 is not running on my machine. Both the 32/64 bit builds of InVesalius...

``` Dear Dave, Thanks for stopping by! The DICOMReader sorts all DICOM slices according to their Imahge Position Patient (IPP) metadata, that is, their actual relative location in 3D scanner...

``` Charl, Thanks for the quick response. Yes, I guess I meant to say that I had used the DICOMBrowser, and it loads all the slices fine, but the ordering...