DICOM @ OFFIS

The C-MOVE destination AET is missing in the parameters you are passing to the movescu. You need to specify by the -aem parameter. You cannot assume that the server interprets a move request without a given move destination AET as a C-MOVE to the requesting AE (-aet). BTW: Most of the time, the next...

Dear DCMTK developers, a colleague of mine stumbled accross the copyright statement in ofstd/libsrc/tstring.cc. It states that this file is part of the GNU ANSI C++ Library, followed by a reference to the GPL. Looking over the code, this does not appear correct to me, for it just contains test code ...

It does, thank you. I wonder which policy is applied to other libraries which keep the prefix of the version and the ABI version in sync, but that is a different story.

Just a brief follow-up question: Is there a particular reason why the major version in the SONAME (.7) is different from the dcmtk version (.3.6.1). This seems to be somehow unusual, all other libraries that I have come accross so far have a SONAME which is a substring of the full version.

Thank you for your response, Jan!

Hi, I am using the dcmtk-3.6.1_20150924 snapshot on Ubuntu Linux. I am using other libraries as well which are not affected by the problem I am going to describe. All dcmtk shared libraries are affected, I am just using dcmdata here in my description to keep it short. After sudo make install If find...

We use the DVT tool (http://dicom.dvtk.org/modules/wiwimod/i ... =downloads) to produce erroneus situations with DICOM implementations. The tests are set up through a high-level scripting language which can simulate any communication behavior with a few lines of code.

Hi Jörg, thank you for your quick and helpful reply. I would definitely like to contribute to your great toolkit, so I will take your proposal into serious consideration. However, I am not looking for sophisticated logging features, I rather want to be able to apply important patches to log4cplus in...

Dear OFFIS team, I am using dcmtk in a project wich already uses log4cplus. I have not completely boiled it down yet, but apparently this causes a clash in thread synchronization (something like trying to lock a mutex with the same name twice). My preferred way of solving the issue would be to use t...

Regarding the DICOM standard, both approaches are legal . However, most PACS vendors have a timeout waiting for DIMSE-commands on an open association to protect the server from handle consumption due to faulty implemented clients. Thus, most clients close the association after their current work is ...

The -xf switch needs 2 parameters: the name of the configuration file and a profile within the configuration file to be selected (e.g. "DEFAULT"). Mind, that the profile names are converted to uppercase when being loaded, so you have to specify the profile in uppercase letters - otherwise ...

This can be achieved usinig the configuration file option (-xf). In the config-file that is referenced you can specify in detail, which presentation contexts are proposed by the storescu.

regards

Markus

It just returns a raw buffer containing the bitmap data. You have to create the header yourself according to the parameters you passed into createWindowsDIB()

Hi Marco,

thanks for your reply. I forgot to mention that all tools applied _are_ based on DCMTK 3.5.4.

I will try to contact the Conquest team as you suggested. Thanks for the contact.

Best regards

Markus

Dear DCMTK experts, I am sorry, if this is slightly off-topic, but AFAIK, DCMTK and the CONQUEST Server share some relevant code. I want to "import" (=read and send via loopback) a filesystem that was written by a Conquest DICOM Server. It works fine with some of the images, but some of th...