-
Notifications
You must be signed in to change notification settings - Fork 66
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
average_3d_ffd segmentation fault error #13
Comments
This is probably related to an issue in |
workaround for MIRTK issue: BioMedIA/MIRTK#782 Fix baiwenjia#13
Hello there, thanks very much for your contribution. I modified the code in as you did and it works well for most of ukb data. However, I still got errors in strain analysis by MIRTK for several participants' data as follows:
Could you please help me with this issue? Thanks very much! |
I have the same problem as well in roughly 3-5% of the participants. I tried several things but was unable to fix it so far. This issue seems to be related: BioMedIA/MIRTK#758 |
Thanks for your reply! The strain analysis pipeline will be interrupted and no tabular result will be written when this problem is raised. Is it convenient for you to share the modified code in eval_strain_lax.py and eval_strain_sax.py to fix this problem? I really appreciate your kind help! |
Ah yes, I did not change anything there. Instead, I'm now running each participant individually. So if one fails, that does not affect the others. It also allows better parallelization. But I have to aggregate the results manually in the end. |
I used try-expection code block and it also worked. Thank you!!! |
Hi @Janner125, I'm not sure what's going on there. I also no longer have access to the UK Biobank data. In the case of ED and ES both being 0: if I remember correctly, ED is hard coded to be 0 while ES is the frame with the smallest LV volume. I would suggest to check if the segmentation worked at all in these cases, probably it failed so LV volume is 0 in all frames (just my guess). I have no idea why AAO area is always 0, this requires debugging that I can't do. I hope you find solutions to your problems. |
|
pass the quality control. |
Hi,
I tried running the code both on MacOS and Ubuntu, using the official MIRTK docker image as base image. In both cases I get a seg fault error during execution of the average_3d_ffd program. Seems like the issue is in the nested loop in average_3d_ffd.cc. X, Y and Z are 1 (single control point) for every forward / backward transformation pair except for the very first and the very last pairs. In particular, for the first example, the very first forward transformation from fr00 to fr01 has 29 control points, while the corresponding backward transformation has a single control point, which causes the seg fault error. What is the correct way to fix this issue?
The text was updated successfully, but these errors were encountered: