sorry, I thought I answered this. those slight offsets are not 
important, you can round to nearest TR

On 08/08/2017 10:57 PM, Ruthie Shaffer wrote:
> Hi all,
> I sent a message previously and just wanted to check in one more time 
> about this question (apologies for the repeat message!).
> I’m using Optseq2 to generate stimulus / jitter schedules and, 
> depending on the TR I use, in the output files I see onset times like 
> 124.4001 (instead of 124.4) or 124.7999 (instead of 124.8).
> This is the command I’m using:
> 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 the outputs (does it mean that I’ve 
> specified something incorrectly in the above command), or is it 
> correct to assume that something like 124.4001 just means 124.4?
> Anyway, thank you so much for your help on this!
> Best wishes,
> Ruth Shaffer
> _______________________________________________
> Freesurfer mailing list

Douglas N. Greve, Ph.D.
MGH-NMR Center
Phone Number: 617-724-2358
Fax: 617-726-7422


Freesurfer mailing list

The information in this e-mail is intended only for the person to whom it is
addressed. If you believe this e-mail was sent to you in error and the e-mail
contains patient information, please contact the Partners Compliance HelpLine at . If the e-mail was sent to you in error
but does not contain patient information, please contact the sender and properly
dispose of the e-mail.

Reply via email to