help > Error after pre-processing - too many scans versus rows.
Showing 1-3 of 3 posts
Aug 10, 2018 10:08 PM | Alex Boutet
Error after pre-processing - too many scans versus rows.
Hi,
The pre-processing was successful. However, when moving on to the next step of the analysis, I get the following error:
172 rows, while functional data has 31304 scans; the number of rows of a first-level covariate should equal the number of scans for this subject/session
I used the "default" pre-processing pipeline as well as adding the option of scan removal at the 1st step of the preprocessing. I had a total of 182 volumes to start with.
I am not sure how I end up with so many scans? Is there a step I am doing incorrectly?
Thank you!
The pre-processing was successful. However, when moving on to the next step of the analysis, I get the following error:
172 rows, while functional data has 31304 scans; the number of rows of a first-level covariate should equal the number of scans for this subject/session
I used the "default" pre-processing pipeline as well as adding the option of scan removal at the 1st step of the preprocessing. I had a total of 182 volumes to start with.
I am not sure how I end up with so many scans? Is there a step I am doing incorrectly?
Thank you!
Aug 11, 2018 03:08 PM | Alex Boutet
RE: Error after pre-processing - too many scans versus rows.
To follow up on my last post, it seems the function "removing
functional" causes the problem when added to the default
preprocessing pipelines. Without the functional removal scans, my
number of scans are not multiplied.
Aug 14, 2018 06:08 PM | Julian Dronse
RE: Error after pre-processing - too many scans versus rows.
Hi Alex,
I encountered the same problem (only when removing initial scans). This is a CONN-GUI issue as Alfonso explained. This post and the attached patch fixed it for me!
https://www.nitrc.org/forum/message.php?...
Best wishes
Julian
I encountered the same problem (only when removing initial scans). This is a CONN-GUI issue as Alfonso explained. This post and the attached patch fixed it for me!
https://www.nitrc.org/forum/message.php?...
Best wishes
Julian