DICOM @ OFFIS

The FAQ is still up to date: the network module is not safe for multi-thread applications, neither for SCU nor for SCP usage. However, making the network module (as of DCMTK 3.5.3 which already has certain improvements over 3.5.2) thread-safe for the Win32 platform would be almost trivial - there ar...

See the overloaded definitions of the print() method in various classes derived from DcmObject, e.g. DcmByteString::print, DcmDataset::print, DcmFileFormat::print, DcmItem::print, DcmMetaInfo::print, DcmPixelData::print, DcmPixelSequence::print, DcmPixelItem::print, DcmSequenceOfItems::print, DcmAtt...

Make sure that you compile with -DHAVE_CONFIG_H.

Defining and using a private transfer syntax is possible, of course, but will require modifications in the DCMTK source code: define the UID for the private transfer syntax in dcmdata/include/dcuid.h and adapt the corresponding implementation file in dcmdata/libsrc/dcuid.cc add new transfer syntax t...

The Cygwin port has never really intensively been tested - you may have found a specific bug that only shows on Cygwin, possible due to a difference in behaviour of some system function emulation. Looks like this requires some time and a good debugger, but currently we won't be able to support you w...

With DCMTK 3.5.3, you cannot. Network transmission of JPEG 2000 transfer syntax is not yet supported.

There is no portable way to inspect the content of the index.dat file (the format of which is binary, version and platform specific) other than through the API provided with DCMTK, which also makes sure (through locks) that concurrent accesses to this file do not produce inconsistencies. As a simple...

The DICOM network protocol implements a minimal level of error checking. First of all, DICOM is an application level protocol on top of TCP, and TCP implements a reliable transport channel (re-transmission of lost packets, checksums etc). Furthermore, imagectn performs a (very basic) check whether t...

Without additional details, no. Something seems to be going wrong. But you knew that already.

This means that the sender is violating the DICOM network protocol in a severe way: the two parts that make up a DICOM C-STORE-RQ message (command set and data set) have different presentation context identifiers, something that must never ever happen in the DICOM network protocol.

Check your configuration. With the -aem option movescu transmits a symbolic AETITLE to imagectn, and imagectn resolves this into an IP address and port number from its own config file. In the config file, however, I read port number 10000 whereas movescu seems to be listening on port 10001. This can...

If configure is unable to compute the sizeof char (which sounds like a pretty trivial task), this usually means that something is wrong with the build environment. Most likely something is missing from the LD_LIBRARY_PATH that prevents configure from running the binaries it has compiled and linked. ...

The error message you see indicates that neither HAVE_SSTREAM nor HAVE_STRSTREAM are defined in cfunix.h, which would mean that something has gone severely wrong with the configure process. Re-run DCMTK's configure script, check for errors and inspect the cfunix.h header file that is produces by the...

The modification would affect DcmRLECodecDecoder::decode() in dcmdata/libsrc/dcrleccd.cc, however, this is some fairly complex code and I don't have the time right now to spend a couple of hours on developing a workaround. I will put this on our to-do-list, but cannot promise more at the moment.

This will be added to the next release, I have actually already committed the changes to our internal CVS a couple of weeks ago.