-
Notifications
You must be signed in to change notification settings - Fork 131
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
IndexError: list index out of range (MRIQC never runs longer than 25s) #1087
Comments
This may actually be an error with being unable to find/get the proper raw_info. |
Hi- Just to note, it might be simpler to get the version information using the The output is simpler for the version number, which likely might not even need to be split, for example:
--pt |
@hannahleechoi , how did you generate this singularity image? I wonder how this issue has not popped up within our integration tests. |
@oesteban Sorry for not seeing this earlier! I generated it like this: singularity build np_mriqc_latest.sif docker://nipreps/mriqc:latest I think this specific issue was resolved by removing the binding of /usr/bin and making sure directories are in BIDS format. However, I am still unable to run mriqc. You can see the newer issue here with netstat and 3dinfo: https://neurostars.org/t/bin-netstat-command-not-found-3dinfo-command-not-found-running-through-latest-mriqc-sif/25387 |
It looks again like a conflict of environments, and AFNI's binaries are being shadowed. |
@oesteban Is there a possible way to fix this? Whenever I attempt to run a subject through, this is the furthest I get, and I'm not too sure what to try next. |
I would try to first run it on some local desktop or laptop through docker. Once you have it working on one or two subjects, then try the setup with singularity. This documentation -> https://www.nipreps.org/apps/framework/ can be useful. Please note the two sections following that I linked, one about docker and the other about singularity. |
Thanks Paul for the note, definitely worth updating on the nipype side (very dutifully you already submitted a patch :). However, the singularity container should go with an AFNI version old enough not to enter this error condition. |
FWIW, I also ran into this error:
after building a docker image locally from 5bb5947 on my M1 mac:
checking the afni install gives:
so despite building with the amd architecture (and throwing no errors during the build), some afni libraries appear to be missing. I also ran this on an intel mac (without the This was resolved (for my use case) by pulling the latest docker image rather than building. Hopefully this helps shine some light on what's happening. |
@oesteban @eilidhmacnicol Thank you so much for the suggestions. I tried to run the container through Docker with the BIDS-formatted data on my personal computer. I didn't get the netstat and 3dinfo errors, but I did get an error regarding synthstrip. I copied the crash file below. Some extra info: I pulled the image and ran mriqc with the command below:
It is my first time working with containers, so I am wondering if you have any general tips on getting things to run smoothly. My assumption is that as long as you have a BIDS-valid dataset, MRIQC should work fine. Is this correct? Also, the reason I would like to use MRIQC is because it closely mirrors fMRIPrep which I am using for my project and have working smoothly. I am working with clinical data and would like to choose the best T1w and best functional run prior to running fMRIPrep on the subjects. If you have other recommendations or comments on my approach, please let me know.
|
@hannahleechoi Error code 137 is due to insufficient memory. How much RAM are you devoting to the process (and over how many CPUs)? |
@smeisler Oscar suggested trying to get it work on my personal mac first - the error code makes sense. I felt like it was taking a bit too long to get mriqc working for me, so I decided to handle qc through fmriprep. Thanks for checking in on the issue. |
@hannahleechoi my 2ct:
|
Hi @oesteban -- I'm getting the same IndexError with the latest pre-release for 24.0.0, but maybe it's a conflicting environment issue? I'm using Using the same data and code, I'm not getting any errors with 23.1.0. Maybe one notable feature of my dataset is that it is multiecho, and it seems like the handling for multiecho data has improved since 23.1.0. The IndexError appears starting with 23.1.1. Happy to share data if it's helpful. It's not quite ready for OpenNeuro and public sharing, but maybe I send a few subjects privately via OneDrive or DropBox. Thanks for any help! Best wishes, Here is my code:
Here is the contents of my mriqc_config.json file:
And here is the full output of the error:
|
@DVSneuro I think this is not the same I just released 24.0.0rc2 yesterday -- can you give it a try? We have improved the logging a lot, so there will be a log entry at the beginning telling you about this config file path. |
Thanks, @oesteban -- sorry, I wasn't sure if I should create a new issue for this error. I do get the same error with the 24.0.0rc2 version. I can also confirm that it happens without the config file being used. I got a different error with a different subject (see below). So, just as a sanity check, I tripled checked the bids validator, and there are no errors there. Same error, latest pre-release:
Different subject, new error:
|
@oesteban -- I tried the latest pre-release (rc6), and I'm still getting the same IndexError. I uploaded some of the data to OpenNeuro if you want to take a look (https://openneuro.org/datasets/ds005085). I don't see the error on sub-10006 (no bold scans) or sub-10015 (no multiecho scans), so I wonder if the issue has something to do with how MRIQC is handling multiecho data? |
What happened?
Received an 'IndexError: list index out of range' very early on whenever attempting to run MRIQC.
I have a feeling that it has something to do with the afni version. Please see error output and additional information below.
I am able to run fmriprep just fine.
What command did you use?
What version of fMRIPrep are you running?
MRIQC v23.0.0
How are you running this software?
Singularity
Is your data BIDS valid?
Yes
Are you reusing any previously computed results?
No
Please copy and paste any relevant log output.
Additional information / screenshots
I have a feeling that 'IndexError: list index out of range' might be coming from the afni version.
If I run this command: singularity exec np_mriqc_latest.sif afni -ver, I get: Precompiled binary linux_openmp_64: Aug 19 2022 (Version AFNI_22.2.07 'Marcus Aurelius')
The result for: version_stamp = raw_info.split("\n")[0].split("Version ")[1] would be AFNI_22.2.07 'Marcus Aurelius')
The text was updated successfully, but these errors were encountered: