Repository navigation
DICOM Dataset Transfer Report #32
Replies: 3 comments 2 replies
|
To test DICOM file transfer, I initially tried using a custom-generated dataset of DICOM files. However, this resulted in errors such as "core dumped" or "invalid file." Therefore, I decided to use actual DICOM files instead. At first, I encountered a connection issue because the system was using port 104. After reviewing detailed logs, I identified the problem and modified the port to 1104. I then created a client script to send DICOM files from the dicom_test folder to the dicom_receiver on the server. I plan to conduct one or two more tests under different scenarios and may later update the documentation with the test results. |
|
Yes, the results I shared above for the DICOM transfer were obtained using a dataset of DICOM files downloaded from the same link that you have shared. Could you please review the results for the DICOM transfer once that I have shared above. |
|
Minor suggestion in language: |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Successful Medical Imaging Data Migration to PACS Server
1. Transfer Overview
/home/adminisatator/l4s/dicom_test172.21.4.251:11042. Technical Configuration
Server Setup
Client Transfer Command
3Conclusion
✅ Successful Transfer: All 137 DICOM files were transferred with zero packet loss
✅ L4S Benefits: Low latency (12.5ms RTT) and zero retransmissions observed
✅ Data Integrity: All studies passed DICOM validation checks
**Appendix: Screenshot **
storescpserver logstorescutransfer outputserver

client


All reactions