Please ignore my previous post. I was wrong on so many levels!
Thanks
S
On Fri, Mar 30, 2018 at 8:34 AM, Sarah Cole wrote:
> Hi Doug,
>
> Sure. I have attached an excel sheet.
> I have averaged the signal magnitude across 16 blocks of objects, and 16
> blocks of scenes, separately. Each block
Hi Doug,
Sure. I have attached an excel sheet.
I have averaged the signal magnitude across 16 blocks of objects, and 16
blocks of scenes, separately. Each block has 8 TRs (TR=2).
The top plot is the data with the default -TR/2 delay.
The bottom plot is the data with -2TR delay.
In both plots, we
not sure what you are trying to do. can you send a picture? the default
lag is TR/2
On 3/29/18 2:30 PM, Sarah Cole wrote:
Thanks, Doug.
I added (-4s) delay and plotted the data but I got the same delay as
no shift. Also I did (+4) delay and lost most of the activation.
Do you have any reco
Thanks, Doug.
I added (-4s) delay and plotted the data but I got the same delay as no
shift. Also I did (+4) delay and lost most of the activation.
Do you have any recommendations?
Thanks,
Sarah
On Wed, Mar 28, 2018 at 4:39 PM, Douglas N. Greve
wrote:
> You can use the -delay flag in mkanalys
You can use the -delay flag in mkanalysis-sess
doug
On 03/28/2018 05:35 PM, Sarah Cole wrote:
> Hi Doug,
>
> I have a block design experiment. After analyzing the data and
> plotting the response magnitude across the TRs, we see that there is a
> systematic lag in the response. For example, in
Hi Doug,
I have a block design experiment. After analyzing the data and plotting the
response magnitude across the TRs, we see that there is a systematic lag in
the response. For example, in a 16s block (TR=2s), at TR-1 and TR-2 the
response goes down and then starts rising from TR-3. This is cons
