-
Notifications
You must be signed in to change notification settings - Fork 32
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
MCMDI issues when b0s are not zeros (b=0) #106
Comments
Hey @villalonreina, When you create the dmipy gradient table you can indicate what is the b-value threshold for counting a measurement as a b0. You can avoid this error in the future this way :-) dmipy/dmipy/core/acquisition_scheme.py Line 494 in dcb0916
Let me know if it solves the problem! |
Thanks @rutgerfick. Yes, we have this line in the code already:
Our b-zeros are actually b=5, and the code still crashes, unless we modify the bval file. I tracked the error and it took me to the |
You're right this is a bug. |
merging the fix tomorrow morning, it's really small. |
Hey @villalonreina , please update to the latest version of dmipy and let me know if this solves this particular problem. |
Hi @matteofrigo @rutgerfick
We have been trying to run MCMDI models on UKBB data and we were getting the following error:
After analyzing the error, we found out that the b0s in UKBB are not full b0s, but instead they are b=5.
Hence, there is an issue in
dmipy/signal_models/cylinder_models.py
because of the way it indexes bvals greater than zero (bval > 0). See below:The text was updated successfully, but these errors were encountered: