-
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
Regressor has extra item, causing mismatch #390
Comments
Do you have a pklz crash file? If we can use nipypecli to rerun the node and drop into the debugger, that would be simplest. |
Here is what I have in the working directory that corresponds to the crashing node:
|
I think we emit crashfiles, either in the working directory or the scratch directory. They would start with |
Yes, it should be |
Yes I found the crash files there. |
If it's a From there you can go fitlins/fitlins/interfaces/nistats.py Lines 124 to 130 in 222d9ab
So you'd want to see what |
Ah, I'm sorry I dropped this. Apologies, the way to look at fitlins/fitlins/interfaces/nistats.py Line 92 in 63fcc78
So: >>> pd.read_hdf('/om2/scratch/Sun/smeisler/INSIDE_fmriprep/sub-inside7002/fitlins_wf/loader/run/run-1_subject-inside7002_dense.h5', key='dense') |
Environment
Expected and Observed Behavior
I had run the same basic model (subject-level contrast maps) for different tasks in the same subjects, and it ran fine. The only difference between the models are the
trial_types
and resulting contrast names.I get the following error:
The number of time points in the run is indeed 424, and the confounds.tsv file also as 424 rows (not including the header column), so I am not seeing where this extra column is coming from.
I used the same fMRIPrep version to produce the different tasks, and they completed without errors. So it is unclear why this one task is causing problems while the others are not.
Steps to Reproduce
--cifti-output 91k
flag--space "fsLR" --drop-missing -s 5 --desc-label ""
flags. Error also happens with volumetric data.The text was updated successfully, but these errors were encountered: