DICOM @ OFFIS

Dear forum reader, with the courtesy of the DCMTK team, I am allowed to announce a non-non-commercial DCMTK application here. We are happy to announce the release of DICOMconnect V03.00 which is a high-level DICOM-library for C++ based on DCMTK. DCMTK is a great toolkit – it has been offering robust...

Thank you very much Marco! I somehow missed to understand that the bug refers to *color* images where Bits Stored < Bits Allocated. I agree that this is not a very realistic scenario. Will look at the images anyway - thanks for providing them - but in fact your explanation is enough for me to assess...

Dear DCMTK team and - users, I am trying to assess the impact of known issues in DCMTK on our DCMTK based implementation. It looks fine except for Bug #369 (https://support.dcmtk.org/redmine/issues/369). I am having a hard time understanding what kind of images this bug refers to. So far I have seen...

Thank you very much for all your help, Jörg!

Now that I know that TS conversion ultimately happens upon writing the dataset to a file or a socket, I have completed my testcases and everything works as expected.

---->SOLVED

Thanks again for the great support!

Yes, sorry. checkAndUpdateVR() was what I meant. I have tried saving and loading, and it works fine. To do so, I had to change the call for setting the (8-bit) pixel data to putAndInsertUint8Array() of course. Then I tried: DcmFileFormat file(&dataset); ofResult = file.saveFile("e:\\temp\\ELE.dcm", ...

Thank you for your counter-questions, Jörg. Here are the answers: Short question: why do you call putAndInsertUint16Array() if the pixel data is 8 bits/pixel? Because PS3.5, A.1c says (for TS Implicit Little Endian): Pixel Data (7FE0,0010) has the Value Representation OW and shall be encoded in Litt...

Dear experts, I am currently investigating how the requirements of PS3.5, Appendix A are implemented and whether we have to consider them in our code using DCMTK or if DCMTK has built-in methods doing the job. If I got it correctly, the baseline for Little Endian Implicit/Explicit is: - if the TS is...

It seems that the Move SCP you are talking to just closes the association while it should better return a C-MOVE-Response which is helpful for debugging. But a few guesses of what typically goes wrong in C-MOVE: - the Move Destintation (testAET) must be configured on the Move SCP side. It should res...

Including the header is not the same as linking to the libraries. You need to have the libraries built as ".lib" and potentially ".dll" or ".so" files, and you have to instruct your linker to add them to your project.

The IJG libraries are shipped with DCMTK, so you just compile jpg8, jpg12 and jpg16 and then link to them like you link to other DCMTK libraries as well.

Are you linking to the dcmjpeg and to the IJG libraries?

We have now changed the implementation of DJCodecEncoder::updateDerivationDescription() to: [...] OFCondition result = dataset->putAndInsertString(DCM_DerivationDescription, derivationDescription.c_str()); if (result.good()) { // assume we can cast the codec parameter to what we need DJCodecParamete...

Thank you very much for your assessment, Marco. Meanwhile we have investigated the issue in more detail. We think that the problem is caused by DJCodecEncoder::updateDerivationDescription(), and we found discrepancies between the behavior of the command line tools (dcmcjpeg) and DCMTK integrated in ...

Hi Jörg, thank you very much for your reply. ad 1: Sorry for the confusion. I figured out that the Image Type was not included at all in this case. It was a CR image, for which Image Type is a Type 3 attribute, so the value changed from "<nothing>" to "DERIVED". It is not so nice that this renders t...

[EDIT - moved this question from Installation to General] Dear DCMTK-forum, I have a question about changes which are applied to DICOM image attributes upon (lossy) on-the-fly compression. We can handle the DCMTK good enough to change the behaviour if needed, but we would like to understand the deci...