This type of design is not suitable for optseq2. Furthermore, you only have
100s of task and almost 300s of scan time. This will lead to lots of empty
space. You really need more than 2 conditions per event type.

Best Regards, Donald McLaren
=================
D.G. McLaren, Ph.D.
Research Fellow, Department of Neurology, Massachusetts General Hospital and
Harvard Medical School
Postdoctoral Research Fellow, GRECC, Bedford VA
Website: http://www.martinos.org/~mclaren
Office: (773) 406-2464
=====================
This e-mail contains CONFIDENTIAL INFORMATION which may contain PROTECTED
HEALTHCARE INFORMATION and may also be LEGALLY PRIVILEGED and which is
intended only for the use of the individual or entity named above. If the
reader of the e-mail is not the intended recipient or the employee or agent
responsible for delivering it to the intended recipient, you are hereby
notified that you are in possession of confidential and privileged
information. Any unauthorized use, disclosure, copying or the taking of any
action in reliance on the contents of this information is strictly
prohibited and may be unlawful. If you have received this e-mail
unintentionally, please immediately notify the sender via telephone at (773)
406-2464 or email.

On Thu, Jul 16, 2015 at 6:17 PM, Heeyoung Choo <heeyoung.c...@utoronto.ca>
wrote:

> Hello,
>
> I'm trying to create trial sequences for a slow event related fMRI
> experiment.
> I have 10 classes of stimuli, and each stimulus lasts 5 sec and repeats
> twice in a run.
>
>
> Environment: Linux 3.13.0-35-generic #62-Ubuntu SMP UTC 2014 x86_64 x86_64
> x86_64 GNU/Linux
>
>
> I ran:
>
> ./optseq2 --ntp 144  --tr 2.5 \
> --ev evt1 5 2 --ev evt2 5 2 --ev evt3 5 2 --ev evt4 5 2 --ev evt5 5 2 --ev
> evt6 5 2 --ev evt7 5 2 --ev evt8 5 2 --ev evt9 5 2 --ev evt10 5 2 \
> --nkeep 10 --psdwin 0 20 --o exp_video \
> --tnullmax 25 --tnullmin 7.5 \
> --nsearch 10000
>
> Almost all of the sequences have extremely long NULL at the end of a run,
> like 82.5sec (please see one of sequences below).
> I am aware that optseq2 is for rapid event related fMRI, and wonder if the
> problem is due to specific parameters of my design, or due to a bug. I
> would appreciate any comments or help.
>
> Thank you very much!
>
> Best regards,
> Heeyoung
>
>
>   0.0000    5    5.000   1.0000          evt5
>   5.0000    0    7.500   1.0000          NULL
>  12.5000    9    5.000   1.0000          evt9
>  17.5000    0    7.500   1.0000          NULL
>  25.0000    3    5.000   1.0000          evt3
>  30.0000    0    7.500   1.0000          NULL
>  37.5000   10    5.000   1.0000         evt10
>  42.5000    0   12.500   1.0000          NULL
>  55.0000    7    5.000   1.0000          evt7
>  60.0000    0   10.000   1.0000          NULL
>  70.0000    3    5.000   1.0000          evt3
>  75.0000    0    7.500   1.0000          NULL
>  82.5000    4    5.000   1.0000          evt4
>  87.5000    0   15.000   1.0000          NULL
> 102.5000    6    5.000   1.0000          evt6
> 107.5000    0    7.500   1.0000          NULL
> 115.0000    6    5.000   1.0000          evt6
> 120.0000    0   10.000   1.0000          NULL
> 130.0000    8    5.000   1.0000          evt8
> 135.0000    0   17.500   1.0000          NULL
> 152.5000    1    5.000   1.0000          evt1
> 157.5000    0    7.500   1.0000          NULL
> 165.0000    2    5.000   1.0000          evt2
> 170.0000    0    7.500   1.0000          NULL
> 177.5000   10    5.000   1.0000         evt10
> 182.5000    0    7.500   1.0000          NULL
> 190.0000    8    5.000   1.0000          evt8
> 195.0000    0    7.500   1.0000          NULL
> 202.5000    9    5.000   1.0000          evt9
> 207.5000    0   12.500   1.0000          NULL
> 220.0000    4    5.000   1.0000          evt4
> 225.0000    0    7.500   1.0000          NULL
> 232.5000    7    5.000   1.0000          evt7
> 237.5000    0    7.500   1.0000          NULL
> 245.0000    1    5.000   1.0000          evt1
> 250.0000    0    7.500   1.0000          NULL
> 257.5000    5    5.000   1.0000          evt5
> 262.5000    0   10.000   1.0000          NULL
> 272.5000    2    5.000   1.0000          evt2
> 277.5000    0   82.500   1.0000          NULL
> _______________________________________________
> Freesurfer mailing list
> Freesurfer@nmr.mgh.harvard.edu
> https://mail.nmr.mgh.harvard.edu/mailman/listinfo/freesurfer
>
>
> 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
> http://www.partners.org/complianceline . 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.
>
>
_______________________________________________
Freesurfer mailing list
Freesurfer@nmr.mgh.harvard.edu
https://mail.nmr.mgh.harvard.edu/mailman/listinfo/freesurfer


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
http://www.partners.org/complianceline . 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