set several TMS pulses during a display that has random duration

[Mariam Kostandyan]

Dear all, 

I am new to the E-Prime, so I am now struggling now a bit with the timing settings of TMS pulses. 

Here, you can see my trial sequence: 

I want to TMS participants 200 ms before the CuePr (CuePr duration = 500 ms), so during the FixCrossPr text presentation. The duration of the FixCrossPr  is set to random in InLine FixCrossDurPr: FixCrossPr.Duration = Random(1200,1600). I am confused how I should deal with the random duration of the FixCrossPr .

I also have another TMS pulses: 100, 300, and 500 ms after the presentation of the FixCrossPr1 (FixCrossPr1 duration = 700 ms). But here everything is simpler because the duration of the FixCrossPr1 is constant. For this part the TMS triggers are in the InLine TMSingPr: 

'Triggers

If c.GetAttrib("TMS")=1 Then

sleep c.GetAttrib("SOA")

writeport 888, triggercode

sleep 1

writeport 888, 0

sleep 999-c.GetAttrib("SOA")

Else 

writeport  888, triggercode

sleep 1

writeport  888, 0

sleep 999

End If

 As you see I refer to the SOA attribute that indicates the timing of the TMS pulse from the onset of the FixCrossPr1. 

Can you help me, please, with sending the TMS pulse 200 ms before the CuePr?

Best,

Mariam

 

[David McFarlane]

Mariam,

Not clear how you output your TMS triggers -- inline code with
WritePort, OnsetSignal facilities, or Task Events? A full answer would
depend on which mechanism you use.

But generally speaking, you could set the Duration of your FixCrossPr to
200 ms less than the random duration, then output your TMS signal, then
do anything to wait another 200 ms (e.g., a Wait object, or Sleep 200 in
inline code), and then your CuePr.

-- David McFarlane

On 2017-06-28 11:01 AM, Mariam Kostandyan wrote:
> Dear all,
>
> I am new to the E-Prime, so I am now struggling now a bit with the
> timing settings of TMS pulses.
>
> Here, you can see my trial sequence:
>

> <https://lh3.googleusercontent.com/-cYJcNdkxZfk/WVPDOyOH3iI/AAAAAAAAAVY/ICMXP5QwyGI9JrBAO81VC64HVyKK3pLcQCLcBGAs/s1600/Untitled.png>
>
>
>
> I want to TMS participants 200 ms before the *CuePr *(*CuePr *duration =
> 500 ms), so during the *FixCrossPr *text presentation. The duration of
> the *FixCrossPr *is set to random in InLine *FixCrossDurPr*:
> /FixCrossPr.Duration = Random(1200,1600). /I am confused how I should
> deal with the random duration of the//*FixCrossPr .*

>
>
> I also have another TMS pulses: 100, 300, and 500 ms after the

> presentation of the *FixCrossPr1 (**FixCrossPr1 *duration = 700 ms). But
> here everything is simpler because the duration of the *FixCrossPr1 *is
> constant. For this part the TMS triggers are in the InLine *TMSingPr: *
>
>
> /'Triggers/
>
> /
> /
>
> /
> /
>
> /If c.GetAttrib("TMS")=1 Then/
>
> /sleep c.GetAttrib("SOA")/
>
> /writeport 888, triggercode/
>
> /sleep 1/
>
> /writeport 888, 0/
>
> /sleep 999-c.GetAttrib("SOA")/
>
> /
> /
>
> /Else /
>
> /writeport 888, triggercode/
>
> /sleep 1/
>
> /writeport 888, 0/
>
> /sleep 999/
>
> /End If/

>
>
> As you see I refer to the SOA attribute that indicates the timing of

> the TMS pulse from the onset of the *FixCrossPr1. *
>
> *
> *

>
> Can you help me, please, with sending the TMS pulse 200 ms before the

> *CuePr?*
>
> *
> *
>
> Best,
>
> Mariam

[Mariam Kostandyan]

Hi David, 

I think that's where the problem is because I simply don't have it for now. Since I am quite new to the E-Prime, I don't know what to use: inline codes, OnsetSignal facilities or Task Events. I would chose the inline code with WritePortas (if it is simpler) but I don't know how to do it in this case. However, I am open to any kind of suggestions! 

Thank you for the tip with making the Duration of my FixCrossPr 200 ms less. I will try it. Do you think you could recommend other oprtions?

Best,

Mariam

среда, 5 июля 2017 г., 23:19:47 UTC+3 пользователь McFarlane, David написал:

[David McFarlane]

Mariam,

The Task Events feature offers many advantages over the older & more
primitive WritePort and OnsetSignal facilities, so I advise that you
take some time out to learn how to use Task Events, and then build from
there. You might also search this group for other threads that discuss
Task Events.

-- David McFarlane

>> https://urldefense.proofpoint.com/v2/url?u=https-3A__lh3.googleusercontent.com_-2DcYJcNdkxZfk_WVPDOyOH3iI_AAAAAAAAAVY_ICMXP5QwyGI9JrBAO81VC64HVyKK3pLcQCLcBGAs_s1600_Untitled.png&d=DwIFaQ&c=nE__W8dFE-shTxStwXtp0A&r=rVCe0bDlnqQHHAg2cizkHg&m=FfHFnVieCoKnca5LapIqMvy8bbL2eoNgSh3JQlnezbg&s=QpItKdp68bcvyF2BXU49vM2wQnegstG_sFV_xdpxc-w&e= >