DICOM @ OFFIS

I am using movescu in my perl script. Is there any way I can know if my call to movescu is success or failure? I tried to pipe like movescu ...... | grep "DIMSE Status : 0x0000: Success" but it nothing happened. I tried to redirect output to a file: movescu ...... > status.txt the file, st...

Thank you again, Michael. And yes, MYPACS01 receiver is fully configured at the PACS. From my observation from the processing details, it seems that the bottleneck is the time wasted in waiting for Status=Pending. If the status is success, it transfers the study smooth and pretty quick. Therefore, I...

Thank you again for your response and suggestion, Michael. Here is the command line fired up by my perl script: /usr/local/dicom/bin/movescu -v -S -aem MYPACS01 -aec D250GEPACS -k 0008,0052=STUDY -k 0020,000D="1.2.840.113745.101000.1002000.38984.4641.21346839" 170.215.245.169 4100 My scrip...

Thank you Michael for your response and suggestion. I did try movescu manually on a single study to see its performance. That study contains only four images. It took more than 10 minutes to have the first Status=Pending message returned. It took more than 10 minutes on every Status=Pending for 3 or...

Sorry. I thought it would have better chance to get response here because I did not get any response on other thread. I would delete the previous message if I could.

We use movescu inside a while loop in a perl script to pre-fetch priors. In one of our tests, it took more than 20 hours to run . Among the processed studies, there are 21 studies with Status = Success studies, 16 with Status = Warning (SubOperationsCompleteOneOrMoreFailures) and 25 with Status = Re...

We use movescu inside a while loop in a perl script to pre-fetch priors. In one of our tests, it took more than 20 hours to run . Among the processed studies, there are 21 studies with Status = Success studies, 16 with Status = Warning (SubOperationsCompleteOneOrMoreFailures) and 25 with Status = Re...

No, I did not read the part 4 of the DICOM standard. Is the part 4 of the DICOM standard relevant to my question? I did a google search on DICOM standard. This is what I found about the part 4 of DICOM standard: http://www.barco.com/barcoview/downloads/TheDICOMstandard_v2.pdf But I did not find the ...

Thank you all. It is working now. I can use Study Instance UID to C-MOVE a particular study.

It brings me to another question. How can I C-MOVE images of a particular series (series-level) or only a particular image (image-level)?

Thanks a lot.

I can use movescu to C-MOVE studies belonging to a particular patient: movescu -v -P -aem TEST01 -aec D100GEPACS -k 0008,0052=PATIENT -k 0010,0020="10668966" 100.200.240.169 4100 I got error message when I use the following comman to C-MOVE a particular study ID: movescu -v -P -aem TEST01 ...

No, I did not install g++. I only installed gcc. I am working on Linux version of Red Hat Fedora core 8.0.

Will it solve Makefile.def problem if I install g++?

Thanks a lot.

I downloaded the patched movescu and findscu. I also installed GNU gcc compiler. Then I followed the INSTALL instructions. It seem all right when I issued ./configure except this (error) message: [root@Lotus dcmtk-3.5.4]# ./config configure: error: C++ preprocessor "/lib/cpp" fails sanity ...

Thank for your prompt response.

Does it mean if I don't use --add-override-key option, I'll be OK? On the other hand, I have to download the fixed version and build it myself if I intend to use that option.

Your help is much appreciated.

Thanks again, Jörg Riesmeier. May I have one more question: We need to be able to do C-MOVE from inside a perl script. One of our vendors recommends MoveScu.exe of dcmtk. I look into the bin subdirectory of the downloaded executable binaries. I do not see MoveScu.exe (or MoveScu). Is dcmtk the right...

Jörg Riesmeier, thank you for your response. The Linux version we have is Red Hat Fedora 8. The reasons we decide to use the binary package because: We only want to use executables in the toolkit with perl scripts, such as MoveScu.exe. We don't have compiling environment set up yet. We heard from a ...