DICOM @ OFFIS

Also, I changed the DCM_SourceApplicationEntityTitle with metaInfo, but it still doesn't work. Check the API documentation for DcmFileFormat::writeFile() at https://support.dcmtk.org/docs/classDcmFileFormat.html. By default, the content of the meta-header is discarded and a new meta-header is creat...

storescu will return a nonzero return code if anything went wrong. You can use that to determine that the files should not be deleted yet, but the return code as such will not tell you what exactly went wrong or which image was not fully transmitted. Furthermore, running storescu with "sudo&quo...

Concerning your first question: (0002,0016) Source Application Entity Title is an attribute that must only appear in the metaheader, never in the main dataset - it is forbidden there. Try writing it to the metaheader instead of the main dataset. Concerning the second question: If you are compiling w...

I am not aware of any library that would support conversion of color models (PhotometricInterpretation) from any to any. This also does not make too much sense: For display on a monitor, you always need RGB, because that is how screens work Palette Color is essentially a space-efficient encoding for...

By default, in all operating systems a closed listen socket will be kept in the TIME_WAIT state by the operating system for some time, in order to "catch" packets that were sent to that socket and have not yet arrived. On Posix systems (such as Linux), DCMTK explicitly disables this delay ...

If you want DCMTK to convert character sets, then you need to compile it with one of the character set conversion libraries supported, i.e. GNU libiconv or ICU.

This file is defective. It should contain uncompressed pixel data for 17444 frames of 512x512 pixels of 3 bytes per pixel (RGB), i.e. 13,718,519,808 bytes of pixel data (which is not possible in an uncompressed DICOM file). In fact, only 833,617,920 bytes of pixel data are present, less than 10%. Th...

You would have to post a dcmdump output of that file - without that it is difficult to guess what may be the problem. However, based on the warning printed ( computed (4572839936) and stored (277872640) pixel count differ ), the pixel data seems to be incomplete. This is understandable, given that t...

The problem with this image file is that it is compressed with JPEG 2000, and cannot be decompressed. In compressed form, the pixel data already allocates about 3 GBytes of data (17444 frames of 512x512 color pixels). In decompressed form, the image would be 12.8 GBytes large, but uncompressed DICOM...

In general, it is not possible to split a large DICOM multi-frame image into many smaller files without in-depth knowledge of the DICOM standard and the physical parameters of the acquisition device. In brief, I would not recommend this route. Extracting all frames from a (very) large DICOM image is...

I have looked at the test image you provided. Due to the file size, you simply cannot decompress it, because the decompressed pixel data element would be larger than 4 GBytes, the upper limit for (7fe0,0010) Pixel Data in uncompressed format. You can, however, use DcmElement::getUncompressedFrame() ...

I presume that you are working on Linux. The DCMTK build scripts on Linux expect pre-compiled developer versions of the external libraries to be available before CMake is run. For all of these libraries, official development packages exist on most Linux distributions, e.g. on Debian/Ubuntu, you just...

You could use the --exec-on-reception command line option to rename the incoming files after the receive process is complete. As an example, the following command line (for Linux) will cause storescp to append a ".dcm" filename extension only once a file has been completely received and wr...

On the other hand, if this is just a single file you are trying to fix, I would use dcmdump +W and dump2dcm to convert the dataset to a text file, and back, while keeping the pixel data in the binary file created by the dcmdump +W option.

I don't think that changing the UID in the metaheader is a function that is foreseen in DCMTK because the transfer syntax value is directly bound to the encoding used, i.e. if you change transfer syntax to MPEG4, then DCMTK will look for an encoder module that would convert uncompressed pixel data t...