Search found 20 matches
- Mon, 2023-07-31, 10:25
- Forum: DCMTK - General
- Topic: movescu works but no images are stored
- Replies: 1
- Views: 4518
movescu works but no images are stored
I would be grateful if someone could please shed some light on this issue for me please. The following movescu succeed but no images are stored in c:\test folder - similar command works for other dicom nodes: movescu -v -S -k 0008,0052=STUDY -aet CARDIAC1 -aec NNUH_QR_SCP 10.145.92.230 105 -k 0020,0...
- Wed, 2022-09-07, 10:45
- Forum: DCMTK - General
- Topic: Invalid sop instance uid - bad Dicom file
- Replies: 11
- Views: 3369
Re: Invalid sop instance uid - bad Dicom file
Thank you for your help. This was educational for me.
- Tue, 2022-09-06, 14:16
- Forum: DCMTK - General
- Topic: Invalid sop instance uid - bad Dicom file
- Replies: 11
- Views: 3369
Re: Invalid sop instance uid - bad Dicom file
So did i misunderstand the quote below from Dicom documentation?
implementations should not depend on any assumed structure of UIDs and should not attempt to parse UIDs to extract the semantics of some of its components
- Tue, 2022-09-06, 11:44
- Forum: DCMTK - General
- Topic: Invalid sop instance uid - bad Dicom file
- Replies: 11
- Views: 3369
Re: Invalid sop instance uid - bad Dicom file
Sorry to reopen this again. I changed the program to avoid .00. but still the same problem
dcmdump +P SOPInstanceUID test.dcm
(0008,0018) UI [1.2.826.0.1.3680043.2.1012.0.542.06.09.2022.10.50.16] # 52, 1 SOPInstanceUID
dcmdump +P SOPInstanceUID test.dcm
(0008,0018) UI [1.2.826.0.1.3680043.2.1012.0.542.06.09.2022.10.50.16] # 52, 1 SOPInstanceUID
- Tue, 2022-09-06, 10:29
- Forum: DCMTK - General
- Topic: Invalid sop instance uid - bad Dicom file
- Replies: 11
- Views: 3369
Re: Invalid sop instance uid - bad Dicom file
Sorry, ignore my last message. Nothing to do with pydicom, I am a lousy programmer!
- Tue, 2022-09-06, 10:26
- Forum: DCMTK - General
- Topic: Invalid sop instance uid - bad Dicom file
- Replies: 11
- Views: 3369
Re: Invalid sop instance uid - bad Dicom file
I am puzzled. My applcation only changes Study and Series Instance UID. I think the SOPInstanceUId is changed by Pydicom package which is supposed to be the bread and butter of medical image datasets!
- Tue, 2022-09-06, 10:16
- Forum: DCMTK - General
- Topic: Invalid sop instance uid - bad Dicom file
- Replies: 11
- Views: 3369
Re: Invalid sop instance uid - bad Dicom file
Thank you! Mystery solved!
- Tue, 2022-09-06, 07:17
- Forum: DCMTK - General
- Topic: Invalid sop instance uid - bad Dicom file
- Replies: 11
- Views: 3369
Re: Invalid sop instance uid - bad Dicom file
dcmdump +P SOPInstanceUID test.dcm
(0008,0018) UI [1.2.826.0.1.3680043.2.1012.00.637.30.08.2022.11.45.50] # 54, 1 SOPInstanceUID
Thanks for looking into this.
(0008,0018) UI [1.2.826.0.1.3680043.2.1012.00.637.30.08.2022.11.45.50] # 54, 1 SOPInstanceUID
Thanks for looking into this.
- Mon, 2022-09-05, 14:28
- Forum: DCMTK - General
- Topic: Invalid sop instance uid - bad Dicom file
- Replies: 11
- Views: 3369
Invalid sop instance uid - bad Dicom file
The Dicom documentation(https://dicom.nema.org/dicom/2013/output/chtml/part05/chapter_B.html) states that: Because of the flexibility allowed by the DICOM Standard in creating organizationally derived UIDs, implementations should not depend on any assumed structure of UIDs and should not attempt to ...
- Wed, 2022-08-24, 14:02
- Forum: DCMTK - General
- Topic: findscu - Modality is ignored when searching by studydate, patientID and modality
- Replies: 11
- Views: 2464
Re: findscu - Modality is ignored when searching by studydate, patientID and modality
Forgot to thank you for your help - I learned a lot.
- Wed, 2022-08-24, 13:57
- Forum: DCMTK - General
- Topic: findscu - Modality is ignored when searching by studydate, patientID and modality
- Replies: 11
- Views: 2464
Re: findscu - Modality is ignored when searching by studydate, patientID and modality
Sorry, i am not that tech savvy. Wish I was!
- Wed, 2022-08-24, 13:30
- Forum: DCMTK - General
- Topic: findscu - Modality is ignored when searching by studydate, patientID and modality
- Replies: 11
- Views: 2464
Re: findscu - Modality is ignored when searching by studydate, patientID and modality
Output does not change if i include 0008,0060=MR in the series-level query, no matter which modality i select.
- Wed, 2022-08-24, 11:37
- Forum: DCMTK - General
- Topic: findscu - Modality is ignored when searching by studydate, patientID and modality
- Replies: 11
- Views: 2464
Re: findscu - Modality is ignored when searching by studydate, patientID and modality
By the way, in your SERIES-level query you also need to add the Unique Key for this level, which is the Series Instance UID (0020,000E). It appears it works without Series Instance UID. See line D: (0008,0060) CS [MR] # 2, 1 Modality in the output below: All I need is to confirm is that the search ...
- Wed, 2022-08-24, 10:56
- Forum: DCMTK - General
- Topic: findscu - Modality is ignored when searching by studydate, patientID and modality
- Replies: 11
- Views: 2464
Re: findscu - Modality is ignored when searching by studydate, patientID and modality
Thank you for your advice. At the end I had to issue another findscu at the series level to confirm the study's modality: findscu -v -d -S -k QueryRetrieveLevel=SERIES -k 0020,000d="1.2.840.113845.11.1000000001951524609.20210406091830.2551313" -k 0008,0060 -aet MYSCP -aec DICOMSCP 10.145.9...
- Wed, 2022-08-24, 08:05
- Forum: DCMTK - General
- Topic: findscu - Modality is ignored when searching by studydate, patientID and modality
- Replies: 11
- Views: 2464
Re: findscu - Modality is ignored when searching by studydate, patientID and modality
Forgive my ignorance on not having a grip on Dicom information models. I tried -S, -P and -O switches to get the results I wanted but thanks to your reply I now understand that Modality attribute is associated with the Series level. My aim was to use movescu to move a study using known values for Pa...