-
Notifications
You must be signed in to change notification settings - Fork 3
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
PyAFQ failure #129
Comments
Running this on the current state of #131. Crash is the same but now populated with file paths:
|
From the terminal output, this immediately precedes the error:
|
I wonder if this is due to an older pyafq version? I remember this, or a similar error, being discussed here: yeatmanlab/pyAFQ#1156 |
So possibly related... (and meant to post this on Friday but apparently didn't actually hit the button)...
So PyAFQ and MAPMRI, which both run DIPY to generate the ODFs, fail due to |
I personally am in favor of keeping it, because (1) sometimes you just want that much stuff (2) it gives users a hint about how to create custom recon specs that do several things (3) it saves people from inadvertently using wrong NODDI coefficients in gray matter. |
Summary
Piggybacking off of #122, I ran into errors with PyAFQ (
--recon-spec pyqfq_tractometry
). This one seems a bit more challenging/problematic to diagnose and I understand that checking onn = 1
isn't super helpful, but it's where we're at for the moment. Essentially, I'm getting an error that there's a NaN response in the CSD fitting. I haven't tested the MRtrix + PyAFQ pipeline (MRtrix MSMT ACT HSVS took 52 hours and just finished), but I know that I get a valid CSD response function from these data based on the other pipelines, which leads me to believe that something isn't getting passed to the node.Additional details
What were you trying to do?
Test for unanticipated failures.
What did you expect to happen?
Unanticipated failures
What actually happened?
Unanticipated failure
Reproducing the bug
Crash log
The text was updated successfully, but these errors were encountered: