DICOM @ OFFIS

Hi, you're right, dcmodify doesn't allow deletion of tags with group numbers 0000 and 0002. For your purposes you could try to use a combination of dcmdump and dump2dcm to remove the command set tag. You also could remove line 485 to 488 of mdfdman.cc to allow dcmodify to delete such tags. However, ...

A minor addition: With DCMTK 3.5.4, there are some new UID options for dcmodify, that allow to generate new Study, Series and SOP Instance UIDs automatically. So this part of the problem could be solved using dcmodify. Concerning your problems with large pixel data values: Did you noticed the +W opt...

I just noticed, that there is also an entry in the FAQ:

viewtopic.php?t=36

Michael

BMP uses internally b,g,r order for storing the colour components, DICOM uses "standard" RGB (r,g,b) order for RGB images.

Regards,
Michael

Hi Patric, there are the following dependencies: config - (no module dependencies) ofstd - config dcmdata - ofstd dcmimgle - dcmdata [zlib, xml] dcmimage - dcmimgle [tiff, png] dcmjpeg - dcmimage [ijg] dcmsr - dcmdata [xml] dcmsign - dcmdata [openssl] dcmtls - dcmdata [openssl] dcmnet - dcmtls [libw...

No Problem:-) I just saw, that you could have meant the explicit option "automatic data correction" from dcmodifys input options. This option (enabled per default) does some extra correction on tag values as said in dcobject.h: /** This flags defines whether automatic correction should be ...

Hi David, what kind of "tag values associated with the sequence length" do you mean? If you think of automatic group length or item length correction, the the answer is yes. The dcmdata routines automatically recalculate such values when writing the file. If you mean other values, please g...

Hi Bernd!

Just a note: I've tested DCMTK 3.5.4 on Mac OS X Tiger with gcc 4 (default). There you can compile the release without problems. Perhaps you're able to update your compiler to get DCMTK 3.5.4 working out of the box.

Best Regards,
Michael

Both tools support some new command line options (see manpages or documentation at http://support.dcmtk.org/docs ). Additionally some smaller changes and bugfixes were integrated. A complete list of changes can be found in the CHANGES.354 file included in the DCMTK source package ( http://www.dcmtk....

Hi Genghis,

try the other prefer-options (e.g. --prefer-jpeg8 for JPEG Baseline).

Regards,
Michael

Hi, the use of imagectn for 40.000 images and more is not recommended, perhaps not even possible. I can't say for sure, because I'm not very experienced with imagectn code. But there seem to be a few issues to consider: - If the index file reaches a size of 32MB, warnings are printed out to console ...

Hm, first you could use dcmdump from the DCMTK to check, whether your values are set correctly in the file. I'm not experienced with CT images, but you should check in part 3 of the standard, whether the possible values of "Pixel Spacing" are restricted for CT images.

Good luck,
Michael

Hi, Ah, I just discovered that it may be a part of the meta-header, that's why I can't modify it? Yes that's right. Dcmodify can't modify tags in the metaheader and the new dcmodify version in the upcoming release won't allow to specify such a command any more. Is there any way to modify it from a p...

Hi,

perhaps section C.11.2.1.2 in part 3 of the standard might give the right answers;-)

Regards,
Michael

Hi, perhaps you only inserted only one value into the Pixel Spacing Attribute? It has a Value Multiplicity = 2, so you have to enter a pair of values there. In the DCMTK, attribute values with VM>1 are represented by a string with all its value parts separated by a backslash character. So the attrib...