DICOM @ OFFIS

JPEG Baseline, the output format of dcmj2pnm --write-jpeg, is always lossy. In case you want to store the rendered image with best quality, you should use another output format.

Of course, the answer also depends on what you mean by "without losing image quality"...

Thank you for the background information. I was just wondering... now I know :D I'm in this for the long haul, so if you don't mind me asking more compiling questions, I'm more than happy to attempt to compile DCMTK with currently available libraries and see how far I get? Of course, please proceed!

Thank you for your work (so far) and your plan to contribute to our Open Source project! My first question when reading your posting was: what's wrong with the official Ubuntu packages . My second question was: why did you download the source code packages of the external libraries from the DCMTK ft...

I can confirm this issue with DCMTK 3.6.3 on Linux systems (for non-local connections), but neither with DCMTK 3.6.2 nor with DCMTK 3.6.4, so I guess it has been fixed already. Without further analysis, my first guess would be that this issue has been introduced with this commit and fixed with this ...

Yes, this is how I interpret the DICOM standard. I guess it would be better to use the following macro (from "dcmnet/dimse.h") in order to check for a warning DIMSE status code: #define DICOM_WARNING_STATUS(status) ((((status) & 0xf000) == 0xb000) || ((status) == 0x0107) || ((status) == 0x0116)) May...

The DICOM standard states in PS3.4 Section H.2.4: If the SCP does not support the Attribute specified by the SCU, it shall return either a Failure status ("No Such Attribute", code 0105H) or return a Warning status ("Attribute List Error", code 0107H.)). In the case of Warning status, the behavior o...

For uncompressed pixel data, the pixels of a multi-frame image are stored in a sequence of bytes (OB) or words (OW). There is no padding between the individual frames. See DICOM PS3.5 for details.

Please start storescu with option -xy (--propose-jpeg) or use dcmsend instead.

According to the DICOM standard, the transfer syntax of the file meta information header is always "Little Endian Explicit". So, there is no need to change it. The attribute Transfer Syntax UID (0002,0010) in this meta header specifies the transfer syntax of the data set that follows the meta header.

The "status summary" is a feature of the DcmStorageSCU class (and not one of the DcmStorageSCP class): http://git.dcmtk.org/?p=dcmtk.git;a=blo ... =HEAD#l949

I would agree and prefer DcmSCU. When the class DcmFindSCU was introduced it was just a (quick) wrapper around the existing findscu functionality, and DcmSCU was net yet planned at that time. In my opinion, DcmFindSCU should be rewritten based on DcmSCU as we did with DcmStorage (not wrapping the fu...

Great to hear that it works but Calling and Called AE Title should never be the same. AE Titles should be unique within a DICOM network, otherwise C-MOVE, which is one way to do the retrieve, would not work.

If you use "sscp_cppunit" as the called AE title, you should also specify a storage area with this name (i.e. in section "AETable"). See documentation for details. Could it be that you've connected to storescp and not to dcmqrscp? At least you've used port 4722 for your SCU... Btw, the storescp opti...

A DIMSE status code of "0000" means "Success" (i.e. no error, no warning). A DIMSE status of "Bxxx" (16-bit hexadecimal, starting with "B") means a warning. See DICOM standard for details.

So, "((status==0)||((status & 0xf000)==0xb000))" will only be true, if no error occurred.

Could you please post the configuration file that you use for dcmqrscp.