[Dcmlib] Fwd: Elscint's Lossless Rice compression

mathieu mathieu.malaterre at gmail.com
Sat Dec 10 03:43:27 CET 2005


That explain why we see thos weird GE file format. It was only designed
to be kept on the Workstation system....
Anyway gdcm handle them :)
Mathieu

---------- Forwarded message ----------
From: Gilles Mevel
Date: 5 Sep 2002 14:41:18 -0700
Subject: Re: Elscint's Lossless Rice compression
To:

Thanks for this info Yves

I supposed it was something like that.

A few years ago, I discovered also such kind of behaviour on GE side.

Images found on AdW workstations where all stored internally in a
DICOM like manner. They had DICOM datasets in files, stored in
Little Endian Implicit, but pixel data (and only pixel data) were
stored in Big Endian.

I suppose this was done for decoding/display optimization purposes,
as AdW is based on a Big Endian machine (Sun).

They also changed the transfer syntax internally.

In the transfer syntaxes for DICOM storage, they always proposed
this private Xfer syntax. It was of course preferred by other GE
storage SCPs.

Bonne journée

Gilles



 "Yves Martel" <martel AT acm.org> wrote in message
news:<EcJd9.354$6W3.49290 at weber.videotron.net>...
> Bonjour Gilles,
>
> From what I understand, Elscint use their "Lossless Rice" compression
> for the internal storage of the images on the SGI disk.  If you copy
> these images directly from the workstation instead of going through
> the "export" operation of their software, you end up with the unreadable
> compressed file.
>
> At least that's the explanation I saw posted on this group a few month
> ago...
>
> Since the images where not supposed to exist outside their application,
> they didn't see the relevance of divulging their compression scheme.
> But maybe GE isn't so secretive?  Any chance we could get the info
> from them?
> 
> Yves Martel
>





More information about the Dcmlib mailing list