-
-
Notifications
You must be signed in to change notification settings - Fork 47
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
Performance problems with newer MR software version (Siemens) #50
Comments
Maybe those DICOM's are significantly different. Should they have nested DICOM tags, it may make the algorithm slower. |
I think while putting together the headers I noticed the reason for this. Siemens has started to bundle several files with the new software version. With the old versions there are 2561 individual DICOM files per QSM, with the new version only 54 files, but then with correspondingly large files. Thus the header grows to over 6000 lines, whereby these are also nested. |
Here is a sample of the new software version: xa50_sample.txt |
Are you therefore sure that the problem comes from the anonymization and not simply the fact that the files are bigger ? |
Yeah okay, I've checked this and it is almost equally fast. Sorry for the confusion. ds = pydicom.dcmread(filename_new)
elem = ds[0x5200, 0x9229][0][0x0021, 0x10fe][0][0x0021, 0x1019]
print(elem) How can I delete this specific tag with your tools? |
This is a good question, I do not know if it is doable as of now. @pchoisel do you have an idea ? |
Hi, If you want to delete tags that are nested inside a sequence tag, you will have to delete the entire sequence tag. Otherwise, the code would need a bit of modification to delete single tag inside a sequence. |
Closing this for no activity |
I noticed that the anonymizer, when used via Python for a newer MR software version with modified DICOM header (modified with respect to the older versions), is significantly slower than for older MR software versions. I have attached an excerpt from the terminal:
This is the same imaging sequence, just on a different scanner with a newer software version.
The text was updated successfully, but these errors were encountered: