-
Notifications
You must be signed in to change notification settings - Fork 77
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
Inefficient Handling of Images with "Bad" Suffixes #1292
Comments
Hello, Thanks for reporting ! To convert dicom to nifti files, the ADNI-to-BIDS converter uses dcm2niix which is an external package and is responsible for the generation of these suffixes. To prevent the converter from generating these files we would need to verify if dcm2niix can actually convert them before running it. In terms of efficiency the piece of logic to implement here seems to be the same as what is currently done, i. e. generating the files and deleting them. Instead, we have a list of subjects / sessions per modality that are known to cause errors and that should be skipped by our converter. For example, for fieldmaps : clinica/clinica/iotools/converters/adni_to_bids/modality_converters/_fmap.py Lines 173 to 213 in 01f9061
These will be removed systematically from the converter list of subjects/sessions to be converted and not be considered at all. Feel free to open a PR if you think of another solution or if you want to report a session causing problems for a specific subject ! Best, |
Description
This builds upon #1060.
While running the dataset converter for ADNI, it appears that images with unsupported suffixes such as
ADC
,real
, andimaginary
are being generated, only to be removed later. This behavior seems wasteful. A more efficient approach might be to proactively identify and skip these files before processing, rather than generating and deleting them.Logs
Question
Is the improved command creating images with "bad" suffixes (such as
ADC
,real
, andimaginary
), and then deleting them? This seems inefficient. Can the code be optimized to identify these unsupported images ahead of time and avoid generating them in the first place?Expected Behavior
Suggested Improvement
The text was updated successfully, but these errors were encountered: