-
Notifications
You must be signed in to change notification settings - Fork 29
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
Segmentation Fault During Cortical Thickness Extraction on Brain MRI Images Using ANTsPynet #137
Comments
|
@ntustison thank you very much for the reply. I have two questions. Question 01: Question 02: I'm facing these errors for most of my images: Do these errors mean my images do not apply the ANTs pre-processing Pipeline? WARNING: In /project/itksource/Modules/Registration/Metricsv4/include/itkCorrelationImageToImageMetricv4HelperThreader.hxx, line 77 WARNING: In /project/itksource/Modules/Numerics/Optimizersv4/include/itkObjectToObjectMetric.hxx, line 575 .local/lib/python3.10/site-packages/antspynet/utilities/desikan_killiany_tourville_labeling.py:388: RuntimeWarning: |
I have no problem running ADNI data on my machines. Perhaps your system is inadequate for running the DKT pipeline. I can try running a problematic image on my end as a check if you post it. |
Yes, you are right! This is causing on DKT pipeline. dkt = antspynet.desikan_killiany_tourville_labeling(t1, do_preprocessing=True, verbose=True)
I used a pool executor to run images one by one in the subset: **# Use ProcessPoolExecutor for concurrency
I want a suggestion on how can I run the pipeline for more images. Any concurrent processing way to handle the DKT labeling? |
I don't run it using a pool executor. I run it either in a for loop or send the image batch as individual jobs to the cluster. |
@ntustison Actually, I tried simple for loop and iterating through the images but it didn't extract all the images. This is the log: I thought this was due to the memory issue then I used a pool executor to handle one image at a time and that also caused the same problem. All images were not extracted. Just some of the images only. This is the log:
|
This is what happened, it stopped suddenly running after some time. As you said, this is the way I used to iterate the images:
|
I've run the DKT pipeline on thousands of images on my university's cluster in the way I described i.e., on the cluster with submitting each subject processing as a single job.. In fact, here's a recent paper and here's the associated github repo for processing all ~50000 UKBB images. I don't know for a fact that it's a memory issue but this appears to be a system-specific issue. I can only guess what the problem is and can't provide any further support than that. |
@ntustison Thank you so much for the clarification. |
@cookpa @ntustison
I am running cortical thickness extraction for Brain MRI images (a batch of 4000 MRI images) and encountered a segmentation fault during processing.
The script ran successfully for several images but failed for many images: 07/ADNI_003_S_0908_MR_MPR__GradWarp__B1_Correction__N3__Scaled_Br_20081015153156378_S46187_I121108.nii.
The error message I received was:
srun: error: compt374: task 0: Segmentation fault (core dumped)
Is this because of a problem in the MRI image or the computation problem?
Or Allocated memory or CPU cores for the configurations?
The text was updated successfully, but these errors were encountered: