DVTk (Main) :: Forum

"FR" not accepted as value in Patient Orientation [by ldepotter]

Mon, 25 Mar 2013 11:08:23 +0200

DVT:: "FR" not accepted as value in Patient Orientation
Hi,

When I send a mammography image for presentation to DVT with a L-MLO view I get an error stating that the �Patient Orientation� (0020,0020) which has the value �A�,�FR� is incorrect. FR is apparently for part of the list of enumerated values.
However, DICOM states in part 3 C.7.6.1.1.1 Patient Orientation that:

For Patient Orientation each value of the orientation attribute shall contain at least one of the abbreviations. If refinements in the orientation descriptions are to be specified, then they shall be designated by one or two additional abbreviations in each value. Within each value, the abbreviations shall be ordered with the principal orientation designated in the first abbreviations.

See also note 2 that states:

E.g., a medio-lateral oblique projection of the left breast of a human might be encoded with Patient Orientation values of �A\FR� rather than �A\F�, since the plane is obliquely inclined such that the colums are directed both downwards and medially, which for a left breast is towards the right, though the downwards direction is the principal column orientation.

Is there a way to work around this problem in DVT?

Best regards

Ludo

Code for Sync StorageCommit and Async StorageCommit [by ramesh]

Tue, 19 Mar 2013 10:05:44 +0200

Using the library:: Code for Sync StorageCommit and Async StorageCommit
Does anybody has the code to replicate Sync StorageCommit and Async StorageCommit functionality using dvtk sdk APIs?

Shutter Shape = Bitmap indicated as wrong in DVT [by ldepotter]

Mon, 18 Mar 2013 15:41:48 +0200

DVT:: Shutter Shape = Bitmap indicated as wrong in DVT
Hi,

When I send a Grayscale Softcopy Presentation State object to DVT, containing a Bitmap Display Shutter Module (To hide the background of a mammo image), then DVT give�s me back an error that has to do with the "Display Shutter Module".
DVT complains that 0018,1600 Shutter Shape hast the wrong value (= Bitmap).

Below this, in the "Bitmap Display Shutter Module" the same attribute 0018,1600 Shutter Shape with value =Bitmap is indicated as correct. (As expected)

Is this a known problem?

Best regards,

Ludo

Re: VOI LUT Sequence Question [by ldepotter]

Mon, 18 Mar 2013 12:24:20 +0200

DVT:: VOI LUT Sequence Question
Hi Marco,

Did someone already create a ticket for this problem and if yes, what is the status today?

Regards,

Ludo

cannot get pass on failed storage commitment SCP response [by fschroeck]

Thu, 07 Mar 2013 12:26:10 +0200

DVT:: cannot get pass on failed storage commitment SCP response
Hello,
to test our StorageCommitmentSCP we would like to validate the response if the storage commitment fails. The script is attached.
The problem is, that even if the response is negative, DVT wants the ReferencedSOPSequence. In our research in the DICOM standard we came across PS 3.4-2008, Page 174.:
"When a response is negative the field "Referenced SOP Sequence", is not mandatory and should be present only when there is any positive match"

But when running the script, the result is "failed" and DVT says:
"Type 1 (mandatory) attribute (0008,1199) should be present with at least one value."

I have tried the latest DVT version 2.6.8. Is this a bug in DVT or a problem in our script?

Thank you very much!

Re: MPPS Media Validation Failure to recognize SOP Class [by marcokemper]

Thu, 07 Mar 2013 08:26:55 +0200

DVT:: MPPS Media Validation Failure to recognize SOP Class

Hi,

according to DICOM, you can only store SOP instances from storage SOP classes in DICOM files. DVTk is able to validate the content of exactly these DICOM files.

You are trying to validate a MPPS message that has been stored in a pseudo-DICOM file, created by DVTk. This is not a DICOM file according to the DICOM standard. DVTk supports storing MPPS messages in pseudo-DICOM files to be able to store the data set part of a MPPS message for reuse in e.g. test scripts. And as this is not a valid DICOM file as specified by the DICOM standard, DVTk is not able to validate this and you will get the error messages as described by you.

Regards,
Marco

Re: Trying to build DVTk, please help [by marcokemper]

Thu, 07 Feb 2013 10:34:50 +0200

Source code of the library:: Trying to build DVTk, please help
Hi David,

thanks for the info.
I'm not aware of a any adjustment needed to compile under Windows 7...
Maybe another user can give some advice.

What is the reason you are trying to recompile the library?

Regards,
Marco

Re: Trying to build DVTk on windows 7 [by marcokemper]

Thu, 07 Feb 2013 10:24:30 +0200

DVT:: Trying to build DVTk on windows 7
Hi David,

thanks for letting other people know the space problem so fast.

Regards,
Marco

Re: appriciation [by marcokemper]

Thu, 24 Jan 2013 12:36:56 +0200

General:: appriciation

Hi,

which prohibited security are you referring to?

Re: Support in Japanese characters [by marcokemper]

Thu, 24 Jan 2013 12:34:28 +0200

RIS Emulator:: Support in Japanese characters
Hi Eyal,

de DVTk RIS Emulator supports (emulates) MWL and MPPS as a SCP.

I'm assuming you are referring to Modality Worklist support in your question. You can supply the RIS Emulator with MWL C-FIND-RSP pseudo-DICOM files to determine which responses it will send back on a received query. If you make sure that these C-FIND-RSP pseudo-DICOM files contain japanese characters for specific attributes, these will be sent back in the C-FIND-RSP (of course only the attributes that have been queried for).

Hope this helps,
Marco