Hi,
I’m using Optseq2 to generate stimulus / jitter schedules, and, depending on the TR used, in the output timing files I see several event onset times very close to the correct time, but slightly off (for example, something like 124.7999, instead of 124.8). I’ve used the following command to generate timing files:
optseq2 --ntp 75 --tr 3.2 --psdwin 0 22.4 3.2 --ev wordPair 3.2 45 --nkeep 6 --o CRtiming.2017 --nsearch 100000 --tnullmin 0 --tnullmax 6.4
Should I be concerned about optimal onset times that are slightly off from the actual possible onset times based on the TR, or is it correct to assume it should be 124.4, instead of 124.4001 or 125.8, instead of 125.7999, for example?
Thank you in advance for any help on this!
Best wishes,
Ruth Shaffer
those are not concerning, you can just round to the nearest TR
On 8/4/17 12:32 PM, Ruthie Shaffer wrote:
Hi,
I’m using Optseq2 to generate stimulus / jitter schedules, and, depending on the TR used, in the output timing files I see several event onset times very close to the correct time, but slightly off (for example, something like 124.7999, instead of 124.8). I’ve used the following command to generate timing files:
optseq2 --ntp 75 --tr 3.2 --psdwin 0 22.4 3.2 --ev wordPair 3.2 45 --nkeep 6 --o CRtiming.2017 --nsearch 100000 --tnullmin 0 --tnullmax 6.4
Should I be concerned about optimal onset times that are slightly off from the actual possible onset times based on the TR, or is it correct to assume it should be 124.4, instead of 124.4001 or 125.8, instead of 125.7999, for example?
Thank you in advance for any help on this!
Best wishes,
Ruth Shaffer
Freesurfer mailing list Freesurfer@nmr.mgh.harvard.edu https://mail.nmr.mgh.harvard.edu/mailman/listinfo/freesurfer
freesurfer@nmr.mgh.harvard.edu
-
Douglas Greve -
Ruthie Shaffer