Findscu.exe: Change of behaviour in dcmtk-3.6.7-win64-dynamic

All other questions regarding DCMTK

Moderator: Moderator Team

Post Reply
Message
Author
amunaaser
Posts: 25
Joined: Thu, 2020-03-26, 10:29

Findscu.exe: Change of behaviour in dcmtk-3.6.7-win64-dynamic

#1 Post by amunaaser » Wed, 2022-09-28, 11:25

Hi!
Another question related to your suggestion about using dcmtk-3.6.7-win64-dynamic...

Before this version, I used the follwing command with Findscu.exe to find all the studies related to the PatientID 191212121212:
findscu.exe -aet MatlabTest -aec VGRRTG --study -k 0008,0052=STUDY -k 0010,0020=191212121212 -k 0008,0020 -k 0008,0061 -k 0008,1030 -k 0020,000D -k 0010,0010 -k 0020,0010 -k 0008,0030 -k 0010,0020 -k 0010,1030 -k 0008,0090 -k 0008,0062 -k 0010,0030 -k 0008,0080 -k 0008,0050 -k 0040,0007 -k 0008,1050 -v dicom.bfr.vgregion.se 104
and the result was a list of all eximanations for this patient.

Now with dcmtk-3.6.7-win64-dynamic, I get all examinations for everybody (which are then truncated at 5000 by the DICOM-archive)!

What should be changed in this command line in order to get the same result as before?

Best regards
Nasser Hosseini

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

Re: Findscu.exe: Change of behaviour in dcmtk-3.6.7-win64-dynamic

#2 Post by Michael Onken » Wed, 2022-09-28, 11:29

Hi,

so the same call with old and new findscu results in different responses from the server? This is highly unexpected and also unlikely that this has not been found before. Make 100% sure to do the same call and don't cut parameters or so.

Best,
Michael

amunaaser
Posts: 25
Joined: Thu, 2020-03-26, 10:29

Re: Findscu.exe: Change of behaviour in dcmtk-3.6.7-win64-dynamic

#3 Post by amunaaser » Wed, 2022-09-28, 12:14

Hi Michael!

I just did it again:
1-fundscu.exe (file date 2022-05-08 22:57)
findscu.exe -aet MatlabTest -aec VGRRTG --study -k 0008,0052=STUDY -k 0010,0020=191111111111 -k 0008,0020 -k 0008,0061 -k 0008,1030 -k 0020,000D -k 0010,0010 -k 0020,0010 -k 0008,0030 -k 0010,0020 -k 0010,1030 -k 0008,0090 -k 0008,0062 -k 0010,0030 -k 0008,0080 -k 0008,0050 -k 0040,0007 -k 0008,1050 -v dicom.bfr.vgregion.se 104 > kolla_new.txt

2- fundscu.exe (file date 2009-03-11 22:27)
findscu.exe -aet MatlabTest -aec VGRRTG --study -k 0008,0052=STUDY -k 0010,0020=191111111111 -k 0008,0020 -k 0008,0061 -k 0008,1030 -k 0020,000D -k 0010,0010 -k 0020,0010 -k 0008,0030 -k 0010,0020 -k 0010,1030 -k 0008,0090 -k 0008,0062 -k 0010,0030 -k 0008,0080 -k 0008,0050 -k 0040,0007 -k 0008,1050 -v dicom.bfr.vgregion.se 104 > kolla_old.txt

The first one returns "kolla_new.txt" with 5000 posts and "kolla_old.txt" with 5 posts. Exactly the same command with different result!
Last edited by amunaaser on Wed, 2022-09-28, 12:19, edited 1 time in total.

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

Re: Findscu.exe: Change of behaviour in dcmtk-3.6.7-win64-dynamic

#4 Post by Michael Onken » Wed, 2022-09-28, 12:19

Coudl you please try instead of

Code: Select all

findscu ... > kolla_new.txt
this:

Code: Select all

findscu  ... 2>&1 kolla_new.txt
Probably you are looking at an old file (to make sure: delete kolla_new.txt and make sure it is re-created by findscu).

Best,
Michael

amunaaser
Posts: 25
Joined: Thu, 2020-03-26, 10:29

Re: Findscu.exe: Change of behaviour in dcmtk-3.6.7-win64-dynamic

#5 Post by amunaaser » Wed, 2022-09-28, 12:30

It doesn't seem to work with "2>&1"

C:\Depo\Private\Nasser\Doc\MATLAB\Projects\Antaros\BFR2LocME>findscu.exe -aet MatlabTest -aec VGRRTG --study -k 0008,0052=STUDY -k 0010,0020=191111111111 -k 0008,0020 -k 0008,0061 -k 0008,1030 -k 0020,000D -k 0010,0010 -k 0020,0010 -k 0008,0030 -k 0010,0020 -k 0010,1030 -k 0008,0090 -k 0008,0062 -k 0010,0030 -k 0008,0080 -k 0008,0050 -k 0040,0007 -k 0008,1050 -v dicom.bfr.vgregion.se 104 2>&1 kolla_new2.txt
$dcmtk: findscu v3.6.7 2022-04-22 $

findscu: DICOM query (C-FIND) SCU
error: cannot access file: kolla_new2.txt

amunaaser
Posts: 25
Joined: Thu, 2020-03-26, 10:29

Re: Findscu.exe: Change of behaviour in dcmtk-3.6.7-win64-dynamic

#6 Post by amunaaser » Thu, 2022-09-29, 07:38

Hi again!

I can imagine, that this is unexpected but it occurs. Do you have an explanation for this and perhaps a solution for how I could work around it?

Thanks again
Regards
Nasser Hosseini

Michael Onken wrote:
Wed, 2022-09-28, 11:29
Hi,

so the same call with old and new findscu results in different responses from the server? This is highly unexpected and also unlikely that this has not been found before. Make 100% sure to do the same call and don't cut parameters or so.

Best,
Michael

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

Re: Findscu.exe: Change of behaviour in dcmtk-3.6.7-win64-dynamic

#7 Post by Michael Onken » Thu, 2022-09-29, 08:15

Hi,
amunaaser wrote:
Wed, 2022-09-28, 12:30
It doesn't seem to work with "2>&1"
sorry, try findscu ... 2> kolla_new2.txt. (i.e. without the "&"). Make sure you delete the old file first to make sure the findscu call creates it.

Best regards,
Michael

amunaaser
Posts: 25
Joined: Thu, 2020-03-26, 10:29

Re: Findscu.exe: Change of behaviour in dcmtk-3.6.7-win64-dynamic

#8 Post by amunaaser » Thu, 2022-09-29, 08:36

Hi!

"2> " has the same behaviour and besides it doesn't write the stdout to the file. Not only the PatientID´s exams are found but everything else in the archive.
This is really a strange behaviuor!

Regards
Nasser Hosseini

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

Re: Findscu.exe: Change of behaviour in dcmtk-3.6.7-win64-dynamic

#9 Post by Michael Onken » Thu, 2022-09-29, 08:40

Yes, but the actual results are printed to stderr as far as I remember and the & does not create a new file I think.

Anyway, you should use -d on both findscu calls (old and new) and check whether the request (C-FIND-REQ message in the logs) is actually the same.

Best,
Michael

amunaaser
Posts: 25
Joined: Thu, 2020-03-26, 10:29

Re: Findscu.exe: Change of behaviour in dcmtk-3.6.7-win64-dynamic

#10 Post by amunaaser » Thu, 2022-09-29, 09:55

Ok! This is the result with -d for the old one. Where should I look?
The new one is too long to paste here.

Request Parameters:
Our Implementation Class UID: 1.2.276.0.7230010.3.0.3.5.4
Our Implementation Version Name: OFFIS_DCMTK_354
Their Implementation Class UID:
Their Implementation Version Name:
Application Context Name: 1.2.840.10008.3.1.1.1
Calling Application Name: MatlabTest
Called Application Name: VGRRTG
Responding Application Name: resp AP Title
Our Max PDU Receive Size: 16384
Their Max PDU Receive Size: 0
Presentation Contexts:
Context ID: 1 (Proposed)
Abstract Syntax: =FINDStudyRootQueryRetrieveInformationModel
Proposed SCP/SCU Role: Default
Accepted SCP/SCU Role: Default
Proposed Transfer Syntax(es):
=LittleEndianExplicit
=BigEndianExplicit
=LittleEndianImplicit
Requested Extended Negotiation: none
Accepted Extended Negotiation: none
Requested Extended Negotitation of User Identity: none
Extended Negotitation of User Identity Response: none
Constructing Associate RQ PDU
PDU Type: Associate Accept, PDU Length: 195 + 6 bytes PDU header
02 00 00 00 00 c3 00 01 00 00 56 47 52 52 54 47
20 20 20 20 20 20 20 20 20 20 4d 61 74 6c 61 62
54 65 73 74 20 20 20 20 20 20 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 10 00 00 15 31 2e
32 2e 38 34 30 2e 31 30 30 30 38 2e 33 2e 31 2e
31 2e 31 21 00 00 1b 01 00 00 00 40 00 00 13 31
2e 32 2e 38 34 30 2e 31 30 30 30 38 2e 31 2e 32
2e 31 50 00 00 43 51 00 00 04 00 01 00 00 52 00
00 25 31 2e 32 2e 35 32 38 2e 31 2e 31 30 30 31
2e 32 2e 38 30 30 2e 36 2e 32 31 30 2e 34 31 30
30 34 2e 38 34 39 32 55 00 00 0e 45 41 34 20 34
31 30 30 34 2e 38 34 39 32
Association Parameters Negotiated:
Our Implementation Class UID: 1.2.276.0.7230010.3.0.3.5.4
Our Implementation Version Name: OFFIS_DCMTK_354
Their Implementation Class UID: 1.2.528.1.1001.2.800.6.210.41004.8492
Their Implementation Version Name: EA4 41004.8492
Application Context Name: 1.2.840.10008.3.1.1.1
Calling Application Name: MatlabTest
Called Application Name: VGRRTG
Responding Application Name: VGRRTG
Our Max PDU Receive Size: 16384
Their Max PDU Receive Size: 65536
Presentation Contexts:
Context ID: 1 (Accepted)
Abstract Syntax: =FINDStudyRootQueryRetrieveInformationModel
Proposed SCP/SCU Role: Default
Accepted SCP/SCU Role: Default
Accepted Transfer Syntax: =LittleEndianExplicit
Requested Extended Negotiation: none
Accepted Extended Negotiation: none
Requested Extended Negotitation of User Identity: none
Extended Negotitation of User Identity Response: none
DIMSE Command To Send:

# Dicom-Data-Set
# Used TransferSyntax: Unknown Transfer Syntax
(0000,0000) UL 0 # 4, 1 CommandGroupLength
(0000,0002) UI =FINDStudyRootQueryRetrieveInformationModel # 28, 1 AffectedSOPClassUID
(0000,0100) US 32 # 2, 1 CommandField
(0000,0110) US 1 # 2, 1 MessageID
(0000,0700) US 2 # 2, 1 Priority
(0000,0800) US 1 # 2, 1 DataSetType
DIMSE sendDcmDataset: sending 88 bytes
DIMSE sendDcmDataset: sending 154 bytes
DIMSE receiveCommand
DIMSE receiveCommand: 1 pdv's (88 bytes), presID=1
DIMSE Command Received:

# Dicom-Data-Set
# Used TransferSyntax: Little Endian Implicit
(0000,0002) UI =FINDStudyRootQueryRetrieveInformationModel # 28, 1 AffectedSOPClassUID
(0000,0100) US 32800 # 2, 1 CommandField
(0000,0120) US 1 # 2, 1 MessageIDBeingRespondedTo
(0000,0800) US 258 # 2, 1 DataSetType
(0000,0900) US 65280 # 2, 1 Status
DIMSE receiveFileData: 376 bytes read (last: YES)
RESPONSE: 1 (Pending)

# Dicom-Data-Set
# Used TransferSyntax: Little Endian Explicit
(0008,0020) DA [20110824] # 8, 1 StudyDate
(0008,0030) TM [160100] # 6, 1 StudyTime
(0008,0050) SH [SEMSND0000489793] # 16, 1 AccessionNumber
(0008,0052) CS [STUDY ] # 6, 1 QueryRetrieveLevel
(0008,0054) AE [VGRRTG\VGRAVESINAMAM] # 20, 2 RetrieveAETitle
(0008,0056) CS [ONLINE] # 6, 1 InstanceAvailability
(0008,0061) CS [MG] # 2, 1 ModalitiesInStudy
(0008,0080) LO [Avesina AB] # 10, 1 InstitutionName
(0008,0090) PN [VGR ] # 4, 1 ReferringPhysiciansName
(0008,1030) LO [SCR 2-bild ] # 12, 1 StudyDescription
(0008,1050) PN (no value available) # 0, 0 PerformingPhysiciansName
(0010,0010) PN [Testasson ] # 10, 1 PatientsName
(0010,0020) LO [191111111111] # 12, 1 PatientID
(0010,0030) DA [19111111] # 8, 1 PatientsBirthDate
(0020,000d) UI [1.2.752.24.5.4843390.20110824155007.764728] # 42, 1 StudyInstanceUID
(0020,0010) SH [SEMAVE0000764728] # 16, 1 StudyID
(3119,0010) LO [GEHC-IT/Centricity Enterprise Archive/Version 3.0 ] # 50, 1 PrivateCreator
(3119,1054) SL 401 # 4, 1 Unknown Tag & Data
--------
DIMSE receiveCommand
DIMSE receiveCommand: 1 pdv's (88 bytes), presID=1
DIMSE Command Received:

# Dicom-Data-Set
# Used TransferSyntax: Little Endian Implicit
(0000,0002) UI =FINDStudyRootQueryRetrieveInformationModel # 28, 1 AffectedSOPClassUID
(0000,0100) US 32800 # 2, 1 CommandField
(0000,0120) US 1 # 2, 1 MessageIDBeingRespondedTo
(0000,0800) US 258 # 2, 1 DataSetType
(0000,0900) US 65280 # 2, 1 Status
DIMSE receiveFileData: 376 bytes read (last: YES)
RESPONSE: 2 (Pending)

# Dicom-Data-Set
# Used TransferSyntax: Little Endian Explicit
(0008,0020) DA [20110824] # 8, 1 StudyDate
(0008,0030) TM [162800] # 6, 1 StudyTime
(0008,0050) SH [SEMSND0000489793] # 16, 1 AccessionNumber
(0008,0052) CS [STUDY ] # 6, 1 QueryRetrieveLevel
(0008,0054) AE [VGRRTG\VGRAVESINAMAM] # 20, 2 RetrieveAETitle
(0008,0056) CS [ONLINE] # 6, 1 InstanceAvailability
(0008,0061) CS [MG] # 2, 1 ModalitiesInStudy
(0008,0080) LO [Avesina AB] # 10, 1 InstitutionName
(0008,0090) PN [VGR ] # 4, 1 ReferringPhysiciansName
(0008,1030) LO [SCR 2-bild ] # 12, 1 StudyDescription
(0008,1050) PN (no value available) # 0, 0 PerformingPhysiciansName
(0010,0010) PN [Testasson ] # 10, 1 PatientsName
(0010,0020) LO [191111111111] # 12, 1 PatientID
(0010,0030) DA [19111111] # 8, 1 PatientsBirthDate
(0020,000d) UI [1.2.752.24.5.4843390.20110824161449.764730] # 42, 1 StudyInstanceUID
(0020,0010) SH [SEMAVE0000764730] # 16, 1 StudyID
(3119,0010) LO [GEHC-IT/Centricity Enterprise Archive/Version 3.0 ] # 50, 1 PrivateCreator
(3119,1054) SL 401 # 4, 1 Unknown Tag & Data
--------
DIMSE receiveCommand
DIMSE receiveCommand: 1 pdv's (88 bytes), presID=1
DIMSE Command Received:

# Dicom-Data-Set
# Used TransferSyntax: Little Endian Implicit
(0000,0002) UI =FINDStudyRootQueryRetrieveInformationModel # 28, 1 AffectedSOPClassUID
(0000,0100) US 32800 # 2, 1 CommandField
(0000,0120) US 1 # 2, 1 MessageIDBeingRespondedTo
(0000,0800) US 258 # 2, 1 DataSetType
(0000,0900) US 65280 # 2, 1 Status
DIMSE receiveFileData: 380 bytes read (last: YES)
RESPONSE: 3 (Pending)

# Dicom-Data-Set
# Used TransferSyntax: Little Endian Explicit
(0008,0020) DA [20100311] # 8, 1 StudyDate
(0008,0030) TM [151741] # 6, 1 StudyTime
(0008,0050) SH [SEMSND0000489793] # 16, 1 AccessionNumber
(0008,0052) CS [STUDY ] # 6, 1 QueryRetrieveLevel
(0008,0054) AE [VGRRTG\VGRSUMAMO] # 16, 2 RetrieveAETitle
(0008,0056) CS [ONLINE] # 6, 1 InstanceAvailability
(0008,0061) CS [CR] # 2, 1 ModalitiesInStudy
(0008,0080) LO [UNILABS MAMMOGRAFI] # 18, 1 InstitutionName
(0008,0090) PN [VGR ] # 4, 1 ReferringPhysiciansName
(0008,1030) LO [SCR 2-bild ] # 12, 1 StudyDescription
(0008,1050) PN (no value available) # 0, 0 PerformingPhysiciansName
(0010,0010) PN [Testasson ] # 10, 1 PatientsName
(0010,0020) LO [191111111111] # 12, 1 PatientID
(0010,0030) DA [19111111] # 8, 1 PatientsBirthDate
(0020,000d) UI [1.2.752.24.5.4843390.20100211132504.613369] # 42, 1 StudyInstanceUID
(0020,0010) SH [SEMSND0000613369] # 16, 1 StudyID
(3119,0010) LO [GEHC-IT/Centricity Enterprise Archive/Version 3.0 ] # 50, 1 PrivateCreator
(3119,1054) SL 1501 # 4, 1 Unknown Tag & Data
--------
DIMSE receiveCommand
DIMSE receiveCommand: 1 pdv's (88 bytes), presID=1
DIMSE Command Received:

# Dicom-Data-Set
# Used TransferSyntax: Little Endian Implicit
(0000,0002) UI =FINDStudyRootQueryRetrieveInformationModel # 28, 1 AffectedSOPClassUID
(0000,0100) US 32800 # 2, 1 CommandField
(0000,0120) US 1 # 2, 1 MessageIDBeingRespondedTo
(0000,0800) US 258 # 2, 1 DataSetType
(0000,0900) US 65280 # 2, 1 Status
DIMSE receiveFileData: 402 bytes read (last: YES)
RESPONSE: 4 (Pending)

# Dicom-Data-Set
# Used TransferSyntax: Little Endian Explicit
(0008,0005) CS [ISO_IR 100] # 10, 1 SpecificCharacterSet
(0008,0020) DA [20121115] # 8, 1 StudyDate
(0008,0030) TM [080114] # 6, 1 StudyTime
(0008,0050) SH [SERKUN0001607429] # 16, 1 AccessionNumber
(0008,0052) CS [STUDY ] # 6, 1 QueryRetrieveLevel
(0008,0054) AE [VGRRTG\VGRKUNGRTG ] # 18, 2 RetrieveAETitle
(0008,0056) CS [ONLINE] # 6, 1 InstanceAvailability
(0008,0061) CS [CR\SR ] # 6, 2 ModalitiesInStudy
(0008,0080) LO (no value available) # 0, 0 InstitutionName
(0008,0090) PN [Ej inlagd i röntgens reg] # 24, 1 ReferringPhysiciansName
(0008,1030) LO [HANDLED vänster ] # 16, 1 StudyDescription
(0008,1050) PN (no value available) # 0, 0 PerformingPhysiciansName
(0010,0010) PN [Stropp, Kalle ] # 14, 1 PatientsName
(0010,0020) LO [191111111111] # 12, 1 PatientID
(0010,0030) DA [19111111] # 8, 1 PatientsBirthDate
(0020,000d) UI [1.2.752.24.3.249413316.1506308] # 30, 1 StudyInstanceUID
(0020,0010) SH [SERKUN0001271745] # 16, 1 StudyID
(3119,0010) LO [GEHC-IT/Centricity Enterprise Archive/Version 3.0 ] # 50, 1 PrivateCreator
(3119,1054) SL 601 # 4, 1 Unknown Tag & Data
--------
DIMSE receiveCommand
DIMSE receiveCommand: 1 pdv's (88 bytes), presID=1
DIMSE Command Received:

# Dicom-Data-Set
# Used TransferSyntax: Little Endian Implicit
(0000,0002) UI =FINDStudyRootQueryRetrieveInformationModel # 28, 1 AffectedSOPClassUID
(0000,0100) US 32800 # 2, 1 CommandField
(0000,0120) US 1 # 2, 1 MessageIDBeingRespondedTo
(0000,0800) US 258 # 2, 1 DataSetType
(0000,0900) US 65280 # 2, 1 Status
DIMSE receiveFileData: 402 bytes read (last: YES)
RESPONSE: 5 (Pending)

# Dicom-Data-Set
# Used TransferSyntax: Little Endian Explicit
(0008,0005) CS [ISO_IR 100] # 10, 1 SpecificCharacterSet
(0008,0020) DA [20081201] # 8, 1 StudyDate
(0008,0030) TM [154925] # 6, 1 StudyTime
(0008,0050) SH [SERKUN0001300140] # 16, 1 AccessionNumber
(0008,0052) CS [STUDY ] # 6, 1 QueryRetrieveLevel
(0008,0054) AE [VGRRTG\VGRKUNGRTG ] # 18, 2 RetrieveAETitle
(0008,0056) CS [ONLINE] # 6, 1 InstanceAvailability
(0008,0061) CS [CR] # 2, 1 ModalitiesInStudy
(0008,0080) LO (no value available) # 0, 0 InstitutionName
(0008,0090) PN [Okänt namn] # 10, 1 ReferringPhysiciansName
(0008,1030) LO [KNÄLED PÅ VÅRDAVD. vänster] # 26, 1 StudyDescription
(0008,1050) PN (no value available) # 0, 0 PerformingPhysiciansName
(0010,0010) PN [FLADSFL,SOSKOFE ] # 16, 1 PatientsName
(0010,0020) LO [191111111111] # 12, 1 PatientID
(0010,0030) DA (no value available) # 0, 0 PatientsBirthDate
(0020,000d) UI [1.2.752.24.5.1636656856.2008120152458.976968] # 44, 1 StudyInstanceUID
(0020,0010) SH [SERKUN0000976968] # 16, 1 StudyID
(3119,0010) LO [GEHC-IT/Centricity Enterprise Archive/Version 3.0 ] # 50, 1 PrivateCreator
(3119,1054) SL 601 # 4, 1 Unknown Tag & Data
--------
DIMSE receiveCommand
DIMSE receiveCommand: 1 pdv's (88 bytes), presID=1
DIMSE Command Received:

# Dicom-Data-Set
# Used TransferSyntax: Little Endian Implicit
(0000,0002) UI =FINDStudyRootQueryRetrieveInformationModel # 28, 1 AffectedSOPClassUID
(0000,0100) US 32800 # 2, 1 CommandField
(0000,0120) US 1 # 2, 1 MessageIDBeingRespondedTo
(0000,0800) US 257 # 2, 1 DataSetType
(0000,0900) US 0 # 2, 1 Status

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

Re: Findscu.exe: Change of behaviour in dcmtk-3.6.7-win64-dynamic

#11 Post by Michael Onken » Thu, 2022-09-29, 10:07

Thank you, please post everything for the new one before the responses from the server come in (all before the words "DIMSE receiveCommand") or include the 1-2 responses if it fits.

Geert Vandenbussche
Posts: 13
Joined: Tue, 2018-11-13, 09:05

Re: Findscu.exe: Change of behaviour in dcmtk-3.6.7-win64-dynamic

#12 Post by Geert Vandenbussche » Thu, 2022-09-29, 10:40

There's indeed a difference in behaviour between the two versions, but the clue is in having -k 0010,0020 twice.
As '-k 0010,0020=191212121212' and as '-k 0010,0020'. The latter will clear the matching key.

Deleting '-k 0010,0020' from the command line should fix it within the latest release.

amunaaser
Posts: 25
Joined: Thu, 2020-03-26, 10:29

Re: Findscu.exe: Change of behaviour in dcmtk-3.6.7-win64-dynamic

#13 Post by amunaaser » Thu, 2022-09-29, 11:38

Oh, thank you Geert! That was a great observation. Your clue helped actually to solve the mystery. :)
Now these two versions deliver a similar result. It is still a question, why the old version did not react to -k 0010,0020 for being there a second time!

Reagrds
Nasser Hosseini
Geert Vandenbussche wrote:
Thu, 2022-09-29, 10:40
There's indeed a difference in behaviour between the two versions, but the clue is in having -k 0010,0020 twice.
As '-k 0010,0020=191212121212' and as '-k 0010,0020'. The latter will clear the matching key.

Deleting '-k 0010,0020' from the command line should fix it within the latest release.

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

Re: Findscu.exe: Change of behaviour in dcmtk-3.6.7-win64-dynamic

#14 Post by Michael Onken » Thu, 2022-09-29, 12:01

Thanks Geert :idea: !

Post Reply

Who is online

Users browsing this forum: No registered users and 1 guest