|
Dave
|
|
|
Group: Administrators
Posts: 12K,
Visits: 99K
|
+x+x+x+x+x+x+x+x+xI see what you are saying. This is what I want: Fixation 3 sec, Prime word 400ms, Mask 3 sec, Target word Ashley The corresponding /stimulustimes definition, then, would look like this: / stimulustimes = [0=fixation; 3000=prime; 3400=mask; 6400=target] i.e. display "fixation" at t0, display the "prime" 3000ms into the trial, display the "mask" 400ms later, i.e. 3400ms into the trial, display the "target" 3000ms later, i.e. at 6400ms into the trial. If you wish to erase any prior stimuli in-between, you can do / stimulustimes = [0=fixation; 3000=blankscreen, prime; 3400=blankscreen, mask; 6400=blankscreen, target] where "blankscreen" is a <shape> covering the previous stimuli <shape blankscreen> / shape = rectangle / color = white / erase = false / size = (100%, 100%) </shape> Hope this helps. Thank you, that did help! I have it programmed in a test experiment that is abbreviated to just a few practice trails to get it right before changing my entire program. I have ran this twice and it works, however after the two trials are complete the screen appears to "freeze"- Control Q is not working. Any idea what is causing this? Ashley I'd have to see the code. My apologies, I meant to attach it. Here it is. Here's the problem: <trial quininescript_Norbert> /validresponse = ("E", "I") /correctresponse = ("E") / stimulustimes = [0=fixation; 3000=blankscreen, quininescript; 3400=blankscreen, mask; 6400=blankscreen, Norbert] /beginresponseframe = 6400/posttrialpause = 1500 </trial> You've instructed the <trial> to only start accepting responses starting in its 6400th _frame_, i.e. between 1 to 2 _minutes_ into the trial (depending on the display's refresh rate). Your two trials should read: <trial quininescript_Norbert> /validresponse = ("E", "I") /correctresponse = ("E") / stimulustimes = [0=fixation; 3000=blankscreen, quininescript; 3400=blankscreen, mask; 6400=blankscreen, Norbert] /beginresponsetime = 6400/posttrialpause = 1500 </trial> <trial NORmanTM_NORbertTM> /validresponse = ("E", "I") /correctresponse = ("E") /stimulustimes = [0=fixation; 3000=blankscreen, NORmanTM; 3400=blankscreen, mask; 6400=blankscreen, NORbertTM] /beginresponsetime = 6400/posttrialpause = 1500 </trial> So when should the response time begin? I chose 6400 since that was the last time I had. Depends on when you _want_ it to begin. If you wish to measure latency _relative_ to the appearance of the target, theb /beginresponsetime should be set to 6400ms. If you wish to measure latency relative to the appearance of the prime, then /beginresponsetime should be set to 3000ms. I want the next trial to begin immediately following the response to the current trial. > I want the next trial to begin immediately following the response to the current trial. This has nothing to do with /beginresponsetime. If you don't want a noticeable "break" between trials, remove the /posttrialpause.
|
|
|
|
|
ash8787
|
|
|
Group: Forum Members
Posts: 24,
Visits: 44
|
+x+x+x+x+x+x+x+x+x+xI see what you are saying. This is what I want: Fixation 3 sec, Prime word 400ms, Mask 3 sec, Target word Ashley The corresponding /stimulustimes definition, then, would look like this: / stimulustimes = [0=fixation; 3000=prime; 3400=mask; 6400=target] i.e. display "fixation" at t0, display the "prime" 3000ms into the trial, display the "mask" 400ms later, i.e. 3400ms into the trial, display the "target" 3000ms later, i.e. at 6400ms into the trial. If you wish to erase any prior stimuli in-between, you can do / stimulustimes = [0=fixation; 3000=blankscreen, prime; 3400=blankscreen, mask; 6400=blankscreen, target] where "blankscreen" is a <shape> covering the previous stimuli <shape blankscreen> / shape = rectangle / color = white / erase = false / size = (100%, 100%) </shape> Hope this helps. Thank you, that did help! I have it programmed in a test experiment that is abbreviated to just a few practice trails to get it right before changing my entire program. I have ran this twice and it works, however after the two trials are complete the screen appears to "freeze"- Control Q is not working. Any idea what is causing this? Ashley I'd have to see the code. My apologies, I meant to attach it. Here it is. Here's the problem: <trial quininescript_Norbert> /validresponse = ("E", "I") /correctresponse = ("E") / stimulustimes = [0=fixation; 3000=blankscreen, quininescript; 3400=blankscreen, mask; 6400=blankscreen, Norbert] /beginresponseframe = 6400/posttrialpause = 1500 </trial> You've instructed the <trial> to only start accepting responses starting in its 6400th _frame_, i.e. between 1 to 2 _minutes_ into the trial (depending on the display's refresh rate). Your two trials should read: <trial quininescript_Norbert> /validresponse = ("E", "I") /correctresponse = ("E") / stimulustimes = [0=fixation; 3000=blankscreen, quininescript; 3400=blankscreen, mask; 6400=blankscreen, Norbert] /beginresponsetime = 6400/posttrialpause = 1500 </trial> <trial NORmanTM_NORbertTM> /validresponse = ("E", "I") /correctresponse = ("E") /stimulustimes = [0=fixation; 3000=blankscreen, NORmanTM; 3400=blankscreen, mask; 6400=blankscreen, NORbertTM] /beginresponsetime = 6400/posttrialpause = 1500 </trial> So when should the response time begin? I chose 6400 since that was the last time I had. Depends on when you _want_ it to begin. If you wish to measure latency _relative_ to the appearance of the target, theb /beginresponsetime should be set to 6400ms. If you wish to measure latency relative to the appearance of the prime, then /beginresponsetime should be set to 3000ms. I want the next trial to begin immediately following the response to the current trial. > I want the next trial to begin immediately following the response to the current trial. This has nothing to do with /beginresponsetime. If you don't want a noticeable "break" between trials, remove the /posttrialpause. Yes. But in terms of the /beginresponseframe, in this needed? I had it before because I was using stimulus frames, now that I am using stimulus times can I remove this?
|
|
|
|
|
Dave
|
|
|
Group: Administrators
Posts: 12K,
Visits: 99K
|
+x+x+x+x+x+x+x+x+x+x+xI see what you are saying. This is what I want: Fixation 3 sec, Prime word 400ms, Mask 3 sec, Target word Ashley The corresponding /stimulustimes definition, then, would look like this: / stimulustimes = [0=fixation; 3000=prime; 3400=mask; 6400=target] i.e. display "fixation" at t0, display the "prime" 3000ms into the trial, display the "mask" 400ms later, i.e. 3400ms into the trial, display the "target" 3000ms later, i.e. at 6400ms into the trial. If you wish to erase any prior stimuli in-between, you can do / stimulustimes = [0=fixation; 3000=blankscreen, prime; 3400=blankscreen, mask; 6400=blankscreen, target] where "blankscreen" is a <shape> covering the previous stimuli <shape blankscreen> / shape = rectangle / color = white / erase = false / size = (100%, 100%) </shape> Hope this helps. Thank you, that did help! I have it programmed in a test experiment that is abbreviated to just a few practice trails to get it right before changing my entire program. I have ran this twice and it works, however after the two trials are complete the screen appears to "freeze"- Control Q is not working. Any idea what is causing this? Ashley I'd have to see the code. My apologies, I meant to attach it. Here it is. Here's the problem: <trial quininescript_Norbert> /validresponse = ("E", "I") /correctresponse = ("E") / stimulustimes = [0=fixation; 3000=blankscreen, quininescript; 3400=blankscreen, mask; 6400=blankscreen, Norbert] /beginresponseframe = 6400/posttrialpause = 1500 </trial> You've instructed the <trial> to only start accepting responses starting in its 6400th _frame_, i.e. between 1 to 2 _minutes_ into the trial (depending on the display's refresh rate). Your two trials should read: <trial quininescript_Norbert> /validresponse = ("E", "I") /correctresponse = ("E") / stimulustimes = [0=fixation; 3000=blankscreen, quininescript; 3400=blankscreen, mask; 6400=blankscreen, Norbert] /beginresponsetime = 6400/posttrialpause = 1500 </trial> <trial NORmanTM_NORbertTM> /validresponse = ("E", "I") /correctresponse = ("E") /stimulustimes = [0=fixation; 3000=blankscreen, NORmanTM; 3400=blankscreen, mask; 6400=blankscreen, NORbertTM] /beginresponsetime = 6400/posttrialpause = 1500 </trial> So when should the response time begin? I chose 6400 since that was the last time I had. Depends on when you _want_ it to begin. If you wish to measure latency _relative_ to the appearance of the target, theb /beginresponsetime should be set to 6400ms. If you wish to measure latency relative to the appearance of the prime, then /beginresponsetime should be set to 3000ms. I want the next trial to begin immediately following the response to the current trial. > I want the next trial to begin immediately following the response to the current trial. This has nothing to do with /beginresponsetime. If you don't want a noticeable "break" between trials, remove the /posttrialpause. Yes. But in terms of the /beginresponseframe, in this needed? I had it before because I was using stimulus frames, now that I am using stimulus times can I remove this? (1) You should not be using /beginresponse frame if you're working with /stimulu stimes. (2) If anything, use /beginresponse time.
|
|
|
|
|
ash8787
|
|
|
Group: Forum Members
Posts: 24,
Visits: 44
|
+x+x+x+x+x+x+x+x+x+x+x+xI see what you are saying. This is what I want: Fixation 3 sec, Prime word 400ms, Mask 3 sec, Target word Ashley The corresponding /stimulustimes definition, then, would look like this: / stimulustimes = [0=fixation; 3000=prime; 3400=mask; 6400=target] i.e. display "fixation" at t0, display the "prime" 3000ms into the trial, display the "mask" 400ms later, i.e. 3400ms into the trial, display the "target" 3000ms later, i.e. at 6400ms into the trial. If you wish to erase any prior stimuli in-between, you can do / stimulustimes = [0=fixation; 3000=blankscreen, prime; 3400=blankscreen, mask; 6400=blankscreen, target] where "blankscreen" is a <shape> covering the previous stimuli <shape blankscreen> / shape = rectangle / color = white / erase = false / size = (100%, 100%) </shape> Hope this helps. Thank you, that did help! I have it programmed in a test experiment that is abbreviated to just a few practice trails to get it right before changing my entire program. I have ran this twice and it works, however after the two trials are complete the screen appears to "freeze"- Control Q is not working. Any idea what is causing this? Ashley I'd have to see the code. My apologies, I meant to attach it. Here it is. Here's the problem: <trial quininescript_Norbert> /validresponse = ("E", "I") /correctresponse = ("E") / stimulustimes = [0=fixation; 3000=blankscreen, quininescript; 3400=blankscreen, mask; 6400=blankscreen, Norbert] /beginresponseframe = 6400/posttrialpause = 1500 </trial> You've instructed the <trial> to only start accepting responses starting in its 6400th _frame_, i.e. between 1 to 2 _minutes_ into the trial (depending on the display's refresh rate). Your two trials should read: <trial quininescript_Norbert> /validresponse = ("E", "I") /correctresponse = ("E") / stimulustimes = [0=fixation; 3000=blankscreen, quininescript; 3400=blankscreen, mask; 6400=blankscreen, Norbert] /beginresponsetime = 6400/posttrialpause = 1500 </trial> <trial NORmanTM_NORbertTM> /validresponse = ("E", "I") /correctresponse = ("E") /stimulustimes = [0=fixation; 3000=blankscreen, NORmanTM; 3400=blankscreen, mask; 6400=blankscreen, NORbertTM] /beginresponsetime = 6400/posttrialpause = 1500 </trial> So when should the response time begin? I chose 6400 since that was the last time I had. Depends on when you _want_ it to begin. If you wish to measure latency _relative_ to the appearance of the target, theb /beginresponsetime should be set to 6400ms. If you wish to measure latency relative to the appearance of the prime, then /beginresponsetime should be set to 3000ms. I want the next trial to begin immediately following the response to the current trial. > I want the next trial to begin immediately following the response to the current trial. This has nothing to do with /beginresponsetime. If you don't want a noticeable "break" between trials, remove the /posttrialpause. Yes. But in terms of the /beginresponseframe, in this needed? I had it before because I was using stimulus frames, now that I am using stimulus times can I remove this? (1) You should not be using /beginresponse frame if you're working with /stimulu stimes. (2) If anything, use /beginresponse time. Gotcha, that makes complete since. Thank you so much for your help.
|
|
|
|
|
ash8787
|
|
|
Group: Forum Members
Posts: 24,
Visits: 44
|
+x+x+x+x+x+x+x+x+x+x+x+x+xI see what you are saying. This is what I want: Fixation 3 sec, Prime word 400ms, Mask 3 sec, Target word Ashley The corresponding /stimulustimes definition, then, would look like this: / stimulustimes = [0=fixation; 3000=prime; 3400=mask; 6400=target] i.e. display "fixation" at t0, display the "prime" 3000ms into the trial, display the "mask" 400ms later, i.e. 3400ms into the trial, display the "target" 3000ms later, i.e. at 6400ms into the trial. If you wish to erase any prior stimuli in-between, you can do / stimulustimes = [0=fixation; 3000=blankscreen, prime; 3400=blankscreen, mask; 6400=blankscreen, target] where "blankscreen" is a <shape> covering the previous stimuli <shape blankscreen> / shape = rectangle / color = white / erase = false / size = (100%, 100%) </shape> Hope this helps. Thank you, that did help! I have it programmed in a test experiment that is abbreviated to just a few practice trails to get it right before changing my entire program. I have ran this twice and it works, however after the two trials are complete the screen appears to "freeze"- Control Q is not working. Any idea what is causing this? Ashley I'd have to see the code. My apologies, I meant to attach it. Here it is. Here's the problem: <trial quininescript_Norbert> /validresponse = ("E", "I") /correctresponse = ("E") / stimulustimes = [0=fixation; 3000=blankscreen, quininescript; 3400=blankscreen, mask; 6400=blankscreen, Norbert] /beginresponseframe = 6400/posttrialpause = 1500 </trial> You've instructed the <trial> to only start accepting responses starting in its 6400th _frame_, i.e. between 1 to 2 _minutes_ into the trial (depending on the display's refresh rate). Your two trials should read: <trial quininescript_Norbert> /validresponse = ("E", "I") /correctresponse = ("E") / stimulustimes = [0=fixation; 3000=blankscreen, quininescript; 3400=blankscreen, mask; 6400=blankscreen, Norbert] /beginresponsetime = 6400/posttrialpause = 1500 </trial> <trial NORmanTM_NORbertTM> /validresponse = ("E", "I") /correctresponse = ("E") /stimulustimes = [0=fixation; 3000=blankscreen, NORmanTM; 3400=blankscreen, mask; 6400=blankscreen, NORbertTM] /beginresponsetime = 6400/posttrialpause = 1500 </trial> So when should the response time begin? I chose 6400 since that was the last time I had. Depends on when you _want_ it to begin. If you wish to measure latency _relative_ to the appearance of the target, theb /beginresponsetime should be set to 6400ms. If you wish to measure latency relative to the appearance of the prime, then /beginresponsetime should be set to 3000ms. I want the next trial to begin immediately following the response to the current trial. > I want the next trial to begin immediately following the response to the current trial. This has nothing to do with /beginresponsetime. If you don't want a noticeable "break" between trials, remove the /posttrialpause. Yes. But in terms of the /beginresponseframe, in this needed? I had it before because I was using stimulus frames, now that I am using stimulus times can I remove this? (1) You should not be using /beginresponse frame if you're working with /stimulu stimes. (2) If anything, use /beginresponse time. Gotcha, that makes complete since. Thank you so much for your help. One last question. Does text default to Arial 14 pt font? My stimuli (text items) that are not specified as Snell Roundhand font appear to be in Arial 14pt font. <text Normanscript> /fontstyle = ("Snell Roundhand", 16pt, false, true, false, false, 5, 0) / txcolor = (0, 0, 0)/items = ("Norman") /position = (50%, 50%) </text> <text NormanN>
/items = ("Norman")
/position = (50%, 50%)
</text>
|
|
|
|
|
Dave
|
|
|
Group: Administrators
Posts: 12K,
Visits: 99K
|
+x+x+x+x+x+x+x+x+x+x+x+x+x+xI see what you are saying. This is what I want: Fixation 3 sec, Prime word 400ms, Mask 3 sec, Target word Ashley The corresponding /stimulustimes definition, then, would look like this: / stimulustimes = [0=fixation; 3000=prime; 3400=mask; 6400=target] i.e. display "fixation" at t0, display the "prime" 3000ms into the trial, display the "mask" 400ms later, i.e. 3400ms into the trial, display the "target" 3000ms later, i.e. at 6400ms into the trial. If you wish to erase any prior stimuli in-between, you can do / stimulustimes = [0=fixation; 3000=blankscreen, prime; 3400=blankscreen, mask; 6400=blankscreen, target] where "blankscreen" is a <shape> covering the previous stimuli <shape blankscreen> / shape = rectangle / color = white / erase = false / size = (100%, 100%) </shape> Hope this helps. Thank you, that did help! I have it programmed in a test experiment that is abbreviated to just a few practice trails to get it right before changing my entire program. I have ran this twice and it works, however after the two trials are complete the screen appears to "freeze"- Control Q is not working. Any idea what is causing this? Ashley I'd have to see the code. My apologies, I meant to attach it. Here it is. Here's the problem: <trial quininescript_Norbert> /validresponse = ("E", "I") /correctresponse = ("E") / stimulustimes = [0=fixation; 3000=blankscreen, quininescript; 3400=blankscreen, mask; 6400=blankscreen, Norbert] /beginresponseframe = 6400/posttrialpause = 1500 </trial> You've instructed the <trial> to only start accepting responses starting in its 6400th _frame_, i.e. between 1 to 2 _minutes_ into the trial (depending on the display's refresh rate). Your two trials should read: <trial quininescript_Norbert> /validresponse = ("E", "I") /correctresponse = ("E") / stimulustimes = [0=fixation; 3000=blankscreen, quininescript; 3400=blankscreen, mask; 6400=blankscreen, Norbert] /beginresponsetime = 6400/posttrialpause = 1500 </trial> <trial NORmanTM_NORbertTM> /validresponse = ("E", "I") /correctresponse = ("E") /stimulustimes = [0=fixation; 3000=blankscreen, NORmanTM; 3400=blankscreen, mask; 6400=blankscreen, NORbertTM] /beginresponsetime = 6400/posttrialpause = 1500 </trial> So when should the response time begin? I chose 6400 since that was the last time I had. Depends on when you _want_ it to begin. If you wish to measure latency _relative_ to the appearance of the target, theb /beginresponsetime should be set to 6400ms. If you wish to measure latency relative to the appearance of the prime, then /beginresponsetime should be set to 3000ms. I want the next trial to begin immediately following the response to the current trial. > I want the next trial to begin immediately following the response to the current trial. This has nothing to do with /beginresponsetime. If you don't want a noticeable "break" between trials, remove the /posttrialpause. Yes. But in terms of the /beginresponseframe, in this needed? I had it before because I was using stimulus frames, now that I am using stimulus times can I remove this? (1) You should not be using /beginresponse frame if you're working with /stimulu stimes. (2) If anything, use /beginresponse time. Gotcha, that makes complete since. Thank you so much for your help. One last question. Does text default to Arial 14 pt font? My stimuli (text items) that are not specified as Snell Roundhand font appear to be in Arial 14pt font. <text Normanscript> /fontstyle = ("Snell Roundhand", 16pt, false, true, false, false, 5, 0) / txcolor = (0, 0, 0)/items = ("Norman") /position = (50%, 50%) </text> <text NormanN>
/items = ("Norman")
/position = (50%, 50%)
</text> IIRC, if no fontstyle is specified, the default should be 16pt Arial. You can specify a different default fontstyle for the script via the <defaults> element's /fontstyle attribute, e.g. <defaults> / fontstyle = ("Verdana", 3%) ... </defaults>
|
|
|
|
|
ash8787
|
|
|
Group: Forum Members
Posts: 24,
Visits: 44
|
+x+x+x+x+x+x+x+x+x+x+x+x+x+x+xI see what you are saying. This is what I want: Fixation 3 sec, Prime word 400ms, Mask 3 sec, Target word Ashley The corresponding /stimulustimes definition, then, would look like this: / stimulustimes = [0=fixation; 3000=prime; 3400=mask; 6400=target] i.e. display "fixation" at t0, display the "prime" 3000ms into the trial, display the "mask" 400ms later, i.e. 3400ms into the trial, display the "target" 3000ms later, i.e. at 6400ms into the trial. If you wish to erase any prior stimuli in-between, you can do / stimulustimes = [0=fixation; 3000=blankscreen, prime; 3400=blankscreen, mask; 6400=blankscreen, target] where "blankscreen" is a <shape> covering the previous stimuli <shape blankscreen> / shape = rectangle / color = white / erase = false / size = (100%, 100%) </shape> Hope this helps. Thank you, that did help! I have it programmed in a test experiment that is abbreviated to just a few practice trails to get it right before changing my entire program. I have ran this twice and it works, however after the two trials are complete the screen appears to "freeze"- Control Q is not working. Any idea what is causing this? Ashley I'd have to see the code. My apologies, I meant to attach it. Here it is. Here's the problem: <trial quininescript_Norbert> /validresponse = ("E", "I") /correctresponse = ("E") / stimulustimes = [0=fixation; 3000=blankscreen, quininescript; 3400=blankscreen, mask; 6400=blankscreen, Norbert] /beginresponseframe = 6400/posttrialpause = 1500 </trial> You've instructed the <trial> to only start accepting responses starting in its 6400th _frame_, i.e. between 1 to 2 _minutes_ into the trial (depending on the display's refresh rate). Your two trials should read: <trial quininescript_Norbert> /validresponse = ("E", "I") /correctresponse = ("E") / stimulustimes = [0=fixation; 3000=blankscreen, quininescript; 3400=blankscreen, mask; 6400=blankscreen, Norbert] /beginresponsetime = 6400/posttrialpause = 1500 </trial> <trial NORmanTM_NORbertTM> /validresponse = ("E", "I") /correctresponse = ("E") /stimulustimes = [0=fixation; 3000=blankscreen, NORmanTM; 3400=blankscreen, mask; 6400=blankscreen, NORbertTM] /beginresponsetime = 6400/posttrialpause = 1500 </trial> So when should the response time begin? I chose 6400 since that was the last time I had. Depends on when you _want_ it to begin. If you wish to measure latency _relative_ to the appearance of the target, theb /beginresponsetime should be set to 6400ms. If you wish to measure latency relative to the appearance of the prime, then /beginresponsetime should be set to 3000ms. I want the next trial to begin immediately following the response to the current trial. > I want the next trial to begin immediately following the response to the current trial. This has nothing to do with /beginresponsetime. If you don't want a noticeable "break" between trials, remove the /posttrialpause. Yes. But in terms of the /beginresponseframe, in this needed? I had it before because I was using stimulus frames, now that I am using stimulus times can I remove this? (1) You should not be using /beginresponse frame if you're working with /stimulu stimes. (2) If anything, use /beginresponse time. Gotcha, that makes complete since. Thank you so much for your help. One last question. Does text default to Arial 14 pt font? My stimuli (text items) that are not specified as Snell Roundhand font appear to be in Arial 14pt font. <text Normanscript> /fontstyle = ("Snell Roundhand", 16pt, false, true, false, false, 5, 0) / txcolor = (0, 0, 0)/items = ("Norman") /position = (50%, 50%) </text> <text NormanN>
/items = ("Norman")
/position = (50%, 50%)
</text> IIRC, if no fontstyle is specified, the default should be 16pt Arial. You can specify a different default fontstyle for the script via the <defaults> element's /fontstyle attribute, e.g. <defaults> / fontstyle = ("Verdana", 3%) ... </defaults> Ok awesome. I got that updated. If I am trying to check certain points of my experiment, is there a way to run it from a selected point to make sure it is correct? Currently I have to run it all the way through to look at items towards the end. It is very time consuming.
|
|
|
|
|
Dave
|
|
|
Group: Administrators
Posts: 12K,
Visits: 99K
|
+x+x+x+x+x+x+x+x+x+x+x+x+x+x+x+xI see what you are saying. This is what I want: Fixation 3 sec, Prime word 400ms, Mask 3 sec, Target word Ashley The corresponding /stimulustimes definition, then, would look like this: / stimulustimes = [0=fixation; 3000=prime; 3400=mask; 6400=target] i.e. display "fixation" at t0, display the "prime" 3000ms into the trial, display the "mask" 400ms later, i.e. 3400ms into the trial, display the "target" 3000ms later, i.e. at 6400ms into the trial. If you wish to erase any prior stimuli in-between, you can do / stimulustimes = [0=fixation; 3000=blankscreen, prime; 3400=blankscreen, mask; 6400=blankscreen, target] where "blankscreen" is a <shape> covering the previous stimuli <shape blankscreen> / shape = rectangle / color = white / erase = false / size = (100%, 100%) </shape> Hope this helps. Thank you, that did help! I have it programmed in a test experiment that is abbreviated to just a few practice trails to get it right before changing my entire program. I have ran this twice and it works, however after the two trials are complete the screen appears to "freeze"- Control Q is not working. Any idea what is causing this? Ashley I'd have to see the code. My apologies, I meant to attach it. Here it is. Here's the problem: <trial quininescript_Norbert> /validresponse = ("E", "I") /correctresponse = ("E") / stimulustimes = [0=fixation; 3000=blankscreen, quininescript; 3400=blankscreen, mask; 6400=blankscreen, Norbert] /beginresponseframe = 6400/posttrialpause = 1500 </trial> You've instructed the <trial> to only start accepting responses starting in its 6400th _frame_, i.e. between 1 to 2 _minutes_ into the trial (depending on the display's refresh rate). Your two trials should read: <trial quininescript_Norbert> /validresponse = ("E", "I") /correctresponse = ("E") / stimulustimes = [0=fixation; 3000=blankscreen, quininescript; 3400=blankscreen, mask; 6400=blankscreen, Norbert] /beginresponsetime = 6400/posttrialpause = 1500 </trial> <trial NORmanTM_NORbertTM> /validresponse = ("E", "I") /correctresponse = ("E") /stimulustimes = [0=fixation; 3000=blankscreen, NORmanTM; 3400=blankscreen, mask; 6400=blankscreen, NORbertTM] /beginresponsetime = 6400/posttrialpause = 1500 </trial> So when should the response time begin? I chose 6400 since that was the last time I had. Depends on when you _want_ it to begin. If you wish to measure latency _relative_ to the appearance of the target, theb /beginresponsetime should be set to 6400ms. If you wish to measure latency relative to the appearance of the prime, then /beginresponsetime should be set to 3000ms. I want the next trial to begin immediately following the response to the current trial. > I want the next trial to begin immediately following the response to the current trial. This has nothing to do with /beginresponsetime. If you don't want a noticeable "break" between trials, remove the /posttrialpause. Yes. But in terms of the /beginresponseframe, in this needed? I had it before because I was using stimulus frames, now that I am using stimulus times can I remove this? (1) You should not be using /beginresponse frame if you're working with /stimulu stimes. (2) If anything, use /beginresponse time. Gotcha, that makes complete since. Thank you so much for your help. One last question. Does text default to Arial 14 pt font? My stimuli (text items) that are not specified as Snell Roundhand font appear to be in Arial 14pt font. <text Normanscript> /fontstyle = ("Snell Roundhand", 16pt, false, true, false, false, 5, 0) / txcolor = (0, 0, 0)/items = ("Norman") /position = (50%, 50%) </text> <text NormanN>
/items = ("Norman")
/position = (50%, 50%)
</text> IIRC, if no fontstyle is specified, the default should be 16pt Arial. You can specify a different default fontstyle for the script via the <defaults> element's /fontstyle attribute, e.g. <defaults> / fontstyle = ("Verdana", 3%) ... </defaults> Ok awesome. I got that updated. If I am trying to check certain points of my experiment, is there a way to run it from a selected point to make sure it is correct? Currently I have to run it all the way through to look at items towards the end. It is very time consuming. Re. the deleted (on request) post about the amount of text on the debriefing <page>: Yes, there is too much text on that single page for it to be displayed completely. You can either decrease the fontsize (via the <instruct> element's /fontstyle) or split the debriefing info across multiple <page> elements. I.e. <page debrief1> some text... </page> <page debrief2> some more text... </page> <page debrief3> even more text... </page> with <expt> / postinstructions = (debrief1, debrief2, debrief3) ... </expt> Hope this helps.
|
|
|
|
|
ash8787
|
|
|
Group: Forum Members
Posts: 24,
Visits: 44
|
+x+x+x+x+x+x+x+x+x+x+x+x+x+x+x+x+xI see what you are saying. This is what I want: Fixation 3 sec, Prime word 400ms, Mask 3 sec, Target word Ashley The corresponding /stimulustimes definition, then, would look like this: / stimulustimes = [0=fixation; 3000=prime; 3400=mask; 6400=target] i.e. display "fixation" at t0, display the "prime" 3000ms into the trial, display the "mask" 400ms later, i.e. 3400ms into the trial, display the "target" 3000ms later, i.e. at 6400ms into the trial. If you wish to erase any prior stimuli in-between, you can do / stimulustimes = [0=fixation; 3000=blankscreen, prime; 3400=blankscreen, mask; 6400=blankscreen, target] where "blankscreen" is a <shape> covering the previous stimuli <shape blankscreen> / shape = rectangle / color = white / erase = false / size = (100%, 100%) </shape> Hope this helps. Thank you, that did help! I have it programmed in a test experiment that is abbreviated to just a few practice trails to get it right before changing my entire program. I have ran this twice and it works, however after the two trials are complete the screen appears to "freeze"- Control Q is not working. Any idea what is causing this? Ashley I'd have to see the code. My apologies, I meant to attach it. Here it is. Here's the problem: <trial quininescript_Norbert> /validresponse = ("E", "I") /correctresponse = ("E") / stimulustimes = [0=fixation; 3000=blankscreen, quininescript; 3400=blankscreen, mask; 6400=blankscreen, Norbert] /beginresponseframe = 6400/posttrialpause = 1500 </trial> You've instructed the <trial> to only start accepting responses starting in its 6400th _frame_, i.e. between 1 to 2 _minutes_ into the trial (depending on the display's refresh rate). Your two trials should read: <trial quininescript_Norbert> /validresponse = ("E", "I") /correctresponse = ("E") / stimulustimes = [0=fixation; 3000=blankscreen, quininescript; 3400=blankscreen, mask; 6400=blankscreen, Norbert] /beginresponsetime = 6400/posttrialpause = 1500 </trial> <trial NORmanTM_NORbertTM> /validresponse = ("E", "I") /correctresponse = ("E") /stimulustimes = [0=fixation; 3000=blankscreen, NORmanTM; 3400=blankscreen, mask; 6400=blankscreen, NORbertTM] /beginresponsetime = 6400/posttrialpause = 1500 </trial> So when should the response time begin? I chose 6400 since that was the last time I had. Depends on when you _want_ it to begin. If you wish to measure latency _relative_ to the appearance of the target, theb /beginresponsetime should be set to 6400ms. If you wish to measure latency relative to the appearance of the prime, then /beginresponsetime should be set to 3000ms. I want the next trial to begin immediately following the response to the current trial. > I want the next trial to begin immediately following the response to the current trial. This has nothing to do with /beginresponsetime. If you don't want a noticeable "break" between trials, remove the /posttrialpause. Yes. But in terms of the /beginresponseframe, in this needed? I had it before because I was using stimulus frames, now that I am using stimulus times can I remove this? (1) You should not be using /beginresponse frame if you're working with /stimulu stimes. (2) If anything, use /beginresponse time. Gotcha, that makes complete since. Thank you so much for your help. One last question. Does text default to Arial 14 pt font? My stimuli (text items) that are not specified as Snell Roundhand font appear to be in Arial 14pt font. <text Normanscript> /fontstyle = ("Snell Roundhand", 16pt, false, true, false, false, 5, 0) / txcolor = (0, 0, 0)/items = ("Norman") /position = (50%, 50%) </text> <text NormanN>
/items = ("Norman")
/position = (50%, 50%)
</text> IIRC, if no fontstyle is specified, the default should be 16pt Arial. You can specify a different default fontstyle for the script via the <defaults> element's /fontstyle attribute, e.g. <defaults> / fontstyle = ("Verdana", 3%) ... </defaults> Ok awesome. I got that updated. If I am trying to check certain points of my experiment, is there a way to run it from a selected point to make sure it is correct? Currently I have to run it all the way through to look at items towards the end. It is very time consuming. Re. the deleted (on request) post about the amount of text on the debriefing <page>: Yes, there is too much text on that single page for it to be displayed completely. You can either decrease the fontsize (via the <instruct> element's /fontstyle) or split the debriefing info across multiple <page> elements. I.e. <page debrief1> some text... </page> <page debrief2> some more text... </page> <page debrief3> even more text... </page> with <expt> / postinstructions = (debrief1, debrief2, debrief3) ... </expt> Hope this helps. Awesome, thank you! I will try this shortly. Ashley
|
|
|
|