-
Notifications
You must be signed in to change notification settings - Fork 533
FIX Constant column in motion regressor causes singular matrix #1057
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
Conversation
Remove constant column in the motion regressor, caused singular matrix during GLM.
@nathanntg - thanks - this is indeed a bug when used with fsl_glm (especially with the demean flag set to True) |
and while you are at it, would you mind replacing the |
No problem. I'll also update |
@satra - I made similar changes to the other resting state example script, and changed the transform interpolation to linear for both scripts. I tested the revised script up on my data set and it is working correctly. Thanks! |
FIX Constant column in motion regressor causes singular matrix
thanks @nathanntg |
@nathanntg - i'm trying to regenerate the error on some old data and couldn't get it to do so on fsl 5.0.6/7/8 (these are centos distributions). i still think this is a good fix, but it would be good to know what system you are getting the message on. |
Hi @satra - I am using CentOS 6.6 with fsl_glm build 507. I reran the script this morning on one of my data sets and the error message returned is:
Let me know if you want me to try any other configurations or if I should try updating FSL. |
@nathanntg : would it be possible to put those two files ( |
@satra Sorry for the delay, I don't think that I can share the |
plenty of open data sets - search for fcp-indi, nki, abide, etc.,. |
Hi @satra . Unfortunately, I tried a couple of the files from those open data sets and it did not produce the same output. I am not sure what specifically is accounting for the difference. When I looked at the design matrix, nothing jumped out at me. But the "singular matrix" exception was consistent across subjects in our work. Any other ideas I should try to potentially uncover what is going on? |
The constant column in the motion regressor results in the FSL GLM reporting a SingularMatrix exception. I can not find reference to a constant (intercept) term in the
fsl_glm
documentation. It could potentially be a result of the--demean
argument when calling thefsl_glm
command. Do you have any insights into what may be causing this?For now, I am opening the pull request to start discussion. If this seems like a reasonable fix, I will go through the other steps listed in the "contributing" document.