DICOM @ OFFIS

Some other "special" VRs that we use are, for example, for the cases where the DICOM standard says "VR is US, SS or OW". How do you encode that without special handling? Right. My knowledge about DICOM is growing every day (thanks to you guys). If DICOM does not specifiy the dic...

ok.
a pity then that DicomImage looses some info from DiImage.
I'll manage without.

Many thanks!
Kris

yes, this works.
thanks!

can I as for more? it would be nice to have getPixelHeight etc, so be able to use DiImage I guess (I don't need the display stuff of DicomImage). Could someone enlighten me about the difference between DicomImage and DiImage?

sorry. i know I'm being difficult.

Kris

Hi

I've seen lots of posts on gettin gvolumes out of DICOM slices and replies mentioning on how to do this, refering to comp.protocols.dicom.

Reading all this I get very depressed.

Anyone knows if any code on top of DCMTK (ideally with a license similar to DCMTK) that I can use?

Kris Thielemans

Hi I need to read CT images in Hounsfield units. From all the posts on this lists, I figured out that my easiest option would be to use DicomImage("filename") and then getInterData. That works, but I don't have access anymore to the dicom fields such as PixelHeight (and lots of others real...

Hi I've received a bunch of DICOM files with names like i478992.CTDC.64.img. dcmmkdir refuses to read any of these. Looking at this forum I found out that this is because the DICOM Standard only allows 8 char filenames with all uppercase letters etc. After renaming files to i478992 etc, I could make...

Yes, I could load both dictionaries (making sure I first cut out the 'standard' part of the GE dictionary).Thanks. However, I was wondering if it wouldn't be better for DCMTK to be able to use a standard DICOM dictionary as opposed to having its own tweaks. Up to you of course. Thanks a lot for all ...

Hi I notice that in dcmdata/libsrc/dicom.doc you use up as VR for the offsets, e.g. (0004,1400) up OffsetOfTheNextDirectoryRecord 1 dicom98 This seems in conflict with the standard (see http://medical.nema.org/dicom/2004/04_06PU.PDF p.81) which uses UL . I stumbled on this because I am using a dicom...

ok. I see that now (p.40 of http://medical.nema.org/dicom/2004/04_05PU.PDF ): There are three special SQ related Data Elements that are not ruled by the VR encoding rules conveyed by the Transfer Syntax. They shall be encoded as Implicit VR. These special Data Elements are Item (FFFE,E000), Item Del...

yes. You are right. There is no problem with this code.
I guess I was confused by debugging optimised code (or the fact that it was rather late in the night...)

sorry

Kris

Hi I had some problems with a DICOMDIR file so had to do some debugging. I came across the following code (dcmtk 3.5.4) in DcmDicomDir::resolveAllOffsets (dcdicdir.cc line 353) for (unsigned long i = 0; i < maxitems; i++ ) { DcmDirectoryRecord *rec; rec = OFstatic_cast(DcmDirectoryRecord *, localDir...

I found out that my problem is related to the DICOM dictionary that I'm using. If I use dcmtk's dicom.dic everything is fine. The relevant difference between the 2 dictionaries is OFFIS dictionary (FFFE,E000) na Item 1 (FFFE,E00D) na ItemDelimitationItem 1 (FFFE,E0DD) na SequenceDelimitationItem 1 m...

thanks for the suggestion. That gives me .... (0008,1090) LO [Discovery STE] # 14, 1 ManufacturersModelName (0008,1110) SQ (Sequence with undefined length #=0) # u/l, 1 ReferencedStudySequence (fffe,e0dd) UN (SequenceDelimitationItem) # 0, 0 SequenceDelimitationItem and dcmdump then exits (there's s...

Hi I'm trying to read some CT images from a GE Discovery STE. I managed to read them successfully in Analyze (from the Mayo) and matlab, but dcmdump exists after DcmSequenceOfItems: Parse error in sequence, found (fffe,e000) instead of a sequence delimiter from the dictionary (FFFE,E000) UN Item 1 (...