Closed jbwexler closed 1 year ago
Yikes, I just noticed this occurred in several other datasets that I ran. I hadn't noticed because fmriprep still tells me it ran successfully.
I just submitted a ticket to TACC in case they are deleting the fsaverage files.
The fact that this person also had an issue with fsaverage/label makes me think it's an fmriprep issue not a TACC issue.
Tacc just confirmed that they haven't purged any files since last spring.
You're not running multiple processes in the same dataset? It's hard to see how this could happen just from the code, if we can't get a reliable reproduction.
Multiple processes of fmriprep? I'm running subjects in parallel using reproman, nothing has changed with that as far as I'm aware.
Resolved by copying in fsaverage prior to running fmriprep.
This happened for all the subjects I tested, which is not surprising since it seems to result from an issue with fsaverage. This is probably not relevant, but I should note that this run was with --resource-monitor, whereas the last run (which was successful) was without --resource-monitor. Compared to the last run, this datasets's fsaverage is missing the following files:
Here's the crashfile: