Directly extracting information from T_DIMSE_Message?

All other questions regarding DCMTK

Moderator: Moderator Team

Post Reply
Message
Author
vyrus
Posts: 19
Joined: Sat, 2006-01-21, 22:14

Directly extracting information from T_DIMSE_Message?

#1 Post by vyrus »

I am trying to customize the original DCMTK storescp implementation for our application. Is there any way to extract image information (such as # of rows) directly from T_DIMSE_Message object before calling DIMSE_storeProvider?

Michael Onken
DCMTK Developer
Posts: 2049
Joined: Fri, 2004-11-05, 13:47
Location: Oldenburg, Germany
Contact:

#2 Post by Michael Onken »

Hi,

what do you mean by number of rows?

It is not possible to find out the size of the image that is about to received, for example. You only know beforehand the transfer syntax, sop class and sop instance UID of the object.

Does that answer your question :)

Michael

vyrus
Posts: 19
Joined: Sat, 2006-01-21, 22:14

#3 Post by vyrus »

Thank you for the quick response! I am trying (by modifying storescp.cxx) to extract some information from T_DIMSE_Message object after calling DIMSE_receiveCommand but before calling DIMSE_storeProvider, so I can name and direct the received DICOM file to different location. Assuming that after calling DIMSE_receiveCommand, there is some useful information in T_DIMSE_Message for me.

Michael Onken
DCMTK Developer
Posts: 2049
Joined: Fri, 2004-11-05, 13:47
Location: Oldenburg, Germany
Contact:

#4 Post by Michael Onken »

Hi,

ok...so as I wrote there is not much information inside the command set (i.e. T_DIMSE_Message). For C-Store it is defined like quoted below and this is what actually is sent over the wire, not more.

Code: Select all

struct T_DIMSE_C_StoreRQ {
        DIC_US          MessageID;                              /* M */
        DIC_UI          AffectedSOPClassUID;                    /* M */
        T_DIMSE_Priority Priority;                              /* M */
        T_DIMSE_DataSetType DataSetType;                        /* M */
        DIC_UI          AffectedSOPInstanceUID;                 /* M */
        DIC_AE          MoveOriginatorApplicationEntityTitle;   /* U */
        DIC_US          MoveOriginatorID;                       /* U */
        /* DataSet provided as argument to DIMSE functions */   /* M */
        unsigned int    opts; /* which optional items are set */
So no information about the study, the patient, or whatever, only SOP Class and SOP Instance UID are mostly interesting for naming. You only know most characteristics of the image once you received it completely.

Michael

vyrus
Posts: 19
Joined: Sat, 2006-01-21, 22:14

#5 Post by vyrus »

Thank you so much, Michael. I guess I have to reorganize files after receiving. I think that should work fine. Best regards,

Post Reply

Who is online

Users browsing this forum: Bing [Bot] and 1 guest