Skip to content
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

zran_read returned error #85

Closed
cchaswell opened this issue Apr 16, 2021 · 8 comments
Closed

zran_read returned error #85

cchaswell opened this issue Apr 16, 2021 · 8 comments
Assignees
Labels
bug Something isn't working

Comments

@cchaswell
Copy link

What happened?
When I'm in the Halfpipe interface and load in the site's nifti files, I get this error.

Is there an error message?
err_tours.txt

What is the exact command that you used to run Halfpipe?
singularity run --cleanenv --bind /:/ext halfpipe_latest.sif --use-cluster
Which settings did you use?

Please provide the contents of the spec.json file from your Halfpipe working directory. Note that this files contains all information entered in the user interface. If the error that you are reporting occurred in the user interface, the file may not exist.
Does not exist yet.

@cchaswell cchaswell added the bug Something isn't working label Apr 16, 2021
@HippocampusGirl
Copy link
Member

The error occurs when fmriprep tries to load the header of /mnt/BIACnfs/duhsnas-pri.dhe.duke.edu/morey_biac/Lab/Tours/rawdata/sub-COPTSDT09/func/sub-COPTSDT09_task-rest_bold.nii.gz to determine the number of volumes.
Could you try opening the file to see if it is a valid NIfTI image?

@HippocampusGirl
Copy link
Member

If it indeed is an invalid NIfTI image, then we may want to add code to HALFpipe to a) show a warning and then b) exclude the file from analysis.

@cchaswell
Copy link
Author

I do open a few of the niftis and they seem fine in fslview. Is it saying a specific nifti is corrupt, or all of them?

@HippocampusGirl
Copy link
Member

The error refers to the file I mentioned above, so that would be the one to look at :-)

@cchaswell
Copy link
Author

cchaswell commented Apr 16, 2021

I checked all niftis and they look fine. I think I see where the issue is. Can subject names not have an underscore in them? The subjects are labeled like COPTSD_T01.nii.gz. In some of the error log, it is correct. But in the participant list, the underscore is dropped and the program is looking for "COPTSDT01." For this subject set, I do anat/{subject}.nii.gz. It seems like there is an error if an underscore is in the subject variable. I will try it as COPTSD_{subject}.nii.gz but that doesn't always work for other sites.

The subjects are all labeled as COPTSD_T**, but the list looks like this:

Running fMRIPREP version 20.2.1+halfpipe.2:
│ * BIDS dataset path: /ext/mnt/BIACnfs/duhsnas-pri.dhe.duke.edu/morey_biac/Lab/Tours/rawdata.
│ * Participant list: ['COPTSDT01', 'COPTSDT02', 'COPTSDT03', 'COPTSDT04', 'COPTSDT05', 'COPTSDT06', 'COPTSDT07', 'COPTSDT08', 'COPTSDT09', 'COPTSDT10', 'COPTSDT11', 'COPTSDT12', 'COPTSDT13', 'COPTSDT14', 'COPTSDT15', 'COPTSDT16', 'COPTSDT17', 'COPTSDT18', 'COPTSDT19', 'COPTSDT20', 'COPTSDV01', 'COPTSDV02', 'COPTSDV03', 'COPTSDV05', 'COPTSDV06', 'COPTSDV07', 'COPTSDV10', 'COPTSDV11', 'COPTSDV12', 'COPTSDV14', 'COPTSDV15', 'COPTSDV16', 'COPTSDV17', 'COPTSDV18', 'COPTSDV19', 'COPTSDV20', 'COPTSDV22', 'COPTSDV23', 'COPTSDV24', 'COPTSDV25', 'COPTSDV26', 'COPTSDV27'].

@HippocampusGirl
Copy link
Member

I don't think it's about the file names. The error comes from a low-level function for decompressing the .nii.gz and loading it into memory.

I think the next thing to try would be to unzip the input files, i.e. to run something like for i in *.gz; do gunzip $i; done in the folder with the image files.

@HippocampusGirl
Copy link
Member

Ok, I did some more digging. It seems like this is an issue with an older version of indexed_gzip (see pauldmccarthy/indexed_gzip#46). The most recent latest version has upgraded that library, so it should fix this issue. If you have time, it would be great if you could try again with the new version :-)

@HippocampusGirl
Copy link
Member

Will close this for now. Please re-open the issue if it turns out that the new release does not solve the issue :-)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants