-
Notifications
You must be signed in to change notification settings - Fork 295
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DICOM export incomplete - always missing random images #457
Comments
Correction: The series are not complete. Attaching a log file The logged export resulted in 6 Series with a total of 7 pictures (pictures missing in series as well) instead of the desired 14 series of plain x-rays with a total of 29 pictures |
The error message says that there is no SOP Instance UID. Can you put the unlimited stacktrace like in the screenshot here, it might help to get maybe more information.
|
This is what i already did. Its just a absolutely fresh log. Will work a bit with it, force a few CDs an imported files through the export and repost the log. |
Have you tried to import the CD from a folder, not from DICOMDIR and then export? |
Yes. Imported pictures via "CD Import" and "exported"/saved them. Also imported from local folders I manually copied from CDs to drive (the way Im doing it right now) to weasis and exported them to see if it works. It does not. Same results. |
Could you check if the SOP Instance UID value exists in the files that are not exported? see https://weasis.org/en/tutorials/tags |
Could you share a dataset because I cannot reproduce the issue? |
Sorry, call me noob, but i dont really get that question. What kind of dataset. Will do whatever i can |
If you mean a set of dicom images, i can only have a look if i find the old MRI scan of myself and see if it happens with that one too. I think it will, because it happens with every set of images so far. Can take screenshots...whatever... |
Yes, I need data to reproduce the problem. You can send me information to download images via my email. |
I just tested my own mri scans and importing/exporting works flawless. No issue with these, so sharing them might be pointless. Unfortunately I cant share any other data due to mentioned names/lack of anonymisation. |
Unfortunately, I'm not going to investigate further without a procedure to reproduce the problem. You can increase the stacktrace as described above (only 3 lines of error) but I'm not sure you will get more relevant information. |
From the message "Gerät ist nicht bereit", the problem seems to be that the CD is difficult to read. Give it a try:
Some CDs are also extremely slow to read because the files are not physically ordered according to DICOMDIR. |
This issue is closed as it does not concern Weasis. |
Describe the bug. What happened?
Hi Weasis team,
I hope Im not creating a double Report here. I was thinking weasis is the best dicom viewer for my cause as i dicovered a problem that spoils the fun a bit.
I recently discovered the very convenient CD import feature. This works flawless.
After having imported all the needed files I export the files to a folder on my hard drive. Select the Export Dicom feature, select the desired images in the export tree, select "export & close" without altering the options, select the desired folder, done without any error message.
The result of this is not satisfying. The selected files never match the source files, the stacks are always incomplete. It doesnt matter what kind of radiological modality Im exporting. Plain X-Rays are missing the second plain, CT or MRI Scans are missing random images in the exported series. The series are not missing totally.
If you repeat the export process the missing images may fill up (only in random pattern)
The only purpose in creating a github account was posting this question. When adding log files "comment becomes too long" and i cant post this. sorry
Thank you for help!!
What version of Weasis are you running?
4.1.2
On which system the problem occurs?
Windows
Relevant log output
No response
Additional contextual elements
No response
The text was updated successfully, but these errors were encountered: