?That seems to have been the problem: Running the data through Slicer as
suggested elsewhere fixed the slice time code, but then saved only a single
frame of the 4D data. I had been poking around the file header looking for a
corresponding field, not suspecting that it was a calculated value and
Does that run only have 1 time point?
On 04/27/2016 06:29 PM, Mcnorgan, Christopher wrote:
>
> Hi,
>
> First, thanks to Doug Greve for helping me isolate my previous
> problem, which turns out to have resulted from a conflicting fsl
> installation. Now that that's resolved, I'm having a problem
Hi,
First, thanks to Doug Greve for helping me isolate my previous problem, which
turns out to have resulted from a conflicting fsl installation. Now that that's
resolved, I'm having a problem on a first-level analysis.
In preparation for calling selxavg3-sess, I am running preproc-sess on an
