## added latencies are shorter than total timeout

##### added latencies are shorter than total timeout
 Author Message buschmarie          Group: Forum Members Posts: 3, Visits: 4 Dear millisecond team,I have created a program with inquisit lab 5. The subjects received a video as a stimulus and were asked to press a button to indicate what sensations they had. I use the latency times to calculate how long they felt relaxed for example.The video timeout was 1191000ms long in total. If I add up all the latencies of a subject, I get different values. These values are slightly shorter than the total timeout. Here are the added latencies: 1190119, 1190547, 1190959, 1190860 etc.Can you tell me how these different times arise so that I can explain this fact in my study?Many thanks in advance.Kind regards, Annemarie BuschPS.: Here are excerpts from the program so you can understand more easy what I did______________________________________________________________________/items = ("A: keine besondere Empfindung")/position = (10, 98)/txcolor = (0, 0, 0)/font = ("Calibri", -20, 700, 0, 49)/items = ("G: Entspannung")/position = (50, 98)/txcolor = (0, 0, 0)/font = ("Calibri", -20, 700, 0, 49)/items = ("L: Tingles")/position = (90, 98)/txcolor = (0, 0, 0)/font = ("Calibri", -20, 700, 0, 49)/ items= ("Zeit = <% script.currenttime %>")/position = (4, 1)/txcolor = (0, 0, 0)/font = ("Calibri", -20, 700, 0, 49)/items = ("falsche Taste")/select = noreplace/position = (50, 3)/txcolor = (200, 0, 0)/fontstyle = ("Calibri", 2.50%, true, false, false, false, 5, 1)______________________________________________________________________________/inputdevice = keyboard/validresponse = (1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48, 49, 50, 51, 52, 53, 54, 55, 56, 57, 58, 59, 60, 61, 62, 63, 64, 65)/correctresponse = (30, 34, 38)/errormessage = true(error, 400)/branch = [trial.asmr_target_measure]____________________________________________________________________________ /preinstructions = (welcome, how_to1, how_to2, how_to3, instruction1, instruction2)/trials = [1=asmr_target_measure]/bgstim = (asmr_target, reminder_basline_left, reminder_relaxation_middle, reminder_tingling_right, current_time)/timeout = 1191000/postinstructions = (expt_end)/blocks = [1=preinstruction; 2=target; 3=postinstruction]_______________________________________________________________________________/screencolor = (0, 0, 0)/txcolor = (whitesmoke)__________________________________________________________ /txcolor = (255, 255, 255)/screencolor = (0, 0, 0)/fontstyle = ("Calibri", 3.00%, false, false, false, false, 5, 1)/nextkey = (" ")/prevkey = ("p")/nextlabel = "(Leertaste) nächste Seite..."/prevlabel = "(p) vorherige Seite..." Dave posted 5 Months Ago ANSWER         Group: Administrators Posts: 12K, Visits: 89K +x buschmarie - 8/17/2022Dear millisecond team,I have created a program with inquisit lab 5. The subjects received a video as a stimulus and were asked to press a button to indicate what sensations they had. I use the latency times to calculate how long they felt relaxed for example.The video timeout was 1191000ms long in total. If I add up all the latencies of a subject, I get different values. These values are slightly shorter than the total timeout. Here are the added latencies: 1190119, 1190547, 1190959, 1190860 etc.Can you tell me how these different times arise so that I can explain this fact in my study?Many thanks in advance.Kind regards, Annemarie BuschPS.: Here are excerpts from the program so you can understand more easy what I did______________________________________________________________________/items = ("A: keine besondere Empfindung")/position = (10, 98)/txcolor = (0, 0, 0)/font = ("Calibri", -20, 700, 0, 49)/items = ("G: Entspannung")/position = (50, 98)/txcolor = (0, 0, 0)/font = ("Calibri", -20, 700, 0, 49)/items = ("L: Tingles")/position = (90, 98)/txcolor = (0, 0, 0)/font = ("Calibri", -20, 700, 0, 49)/ items= ("Zeit = <% script.currenttime %>")/position = (4, 1)/txcolor = (0, 0, 0)/font = ("Calibri", -20, 700, 0, 49)/items = ("falsche Taste")/select = noreplace/position = (50, 3)/txcolor = (200, 0, 0)/fontstyle = ("Calibri", 2.50%, true, false, false, false, 5, 1)______________________________________________________________________________/inputdevice = keyboard/validresponse = (1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48, 49, 50, 51, 52, 53, 54, 55, 56, 57, 58, 59, 60, 61, 62, 63, 64, 65)/correctresponse = (30, 34, 38)/errormessage = true(error, 400)/branch = [trial.asmr_target_measure]____________________________________________________________________________ /preinstructions = (welcome, how_to1, how_to2, how_to3, instruction1, instruction2)/trials = [1=asmr_target_measure]/bgstim = (asmr_target, reminder_basline_left, reminder_relaxation_middle, reminder_tingling_right, current_time)/timeout = 1191000/postinstructions = (expt_end)/blocks = [1=preinstruction; 2=target; 3=postinstruction]_______________________________________________________________________________/screencolor = (0, 0, 0)/txcolor = (whitesmoke)__________________________________________________________ /txcolor = (255, 255, 255)/screencolor = (0, 0, 0)/fontstyle = ("Calibri", 3.00%, false, false, false, false, 5, 1)/nextkey = (" ")/prevkey = ("p")/nextlabel = "(Leertaste) nächste Seite..."/prevlabel = "(p) vorherige Seite..."The block object has the timeout. Initializing the block object takes time before it starts running the first trial, and it may take a different amount of time on different systems running at different refresh rates -- to draw a stimulus to the screen, Inquisit necessarily has to wait for the start of a dispaly refresh cylce. It cannot draw stimuli while the display is in the middle of a refresh cycle. Same with trial objects. Moreover, your trial has to display error messages for some responses, so that would not be reflected at all when you simply add up latencies. In short, you cannot and should not expect the individual latencies to neatly sum up to exactly the set timeout value. Dave posted 5 Months Ago ANSWER         Group: Administrators Posts: 12K, Visits: 89K +x Dave - 8/17/2022+x buschmarie - 8/17/2022Dear millisecond team,I have created a program with inquisit lab 5. The subjects received a video as a stimulus and were asked to press a button to indicate what sensations they had. I use the latency times to calculate how long they felt relaxed for example.The video timeout was 1191000ms long in total. If I add up all the latencies of a subject, I get different values. These values are slightly shorter than the total timeout. Here are the added latencies: 1190119, 1190547, 1190959, 1190860 etc.Can you tell me how these different times arise so that I can explain this fact in my study?Many thanks in advance.Kind regards, Annemarie BuschPS.: Here are excerpts from the program so you can understand more easy what I did______________________________________________________________________/items = ("A: keine besondere Empfindung")/position = (10, 98)/txcolor = (0, 0, 0)/font = ("Calibri", -20, 700, 0, 49)/items = ("G: Entspannung")/position = (50, 98)/txcolor = (0, 0, 0)/font = ("Calibri", -20, 700, 0, 49)/items = ("L: Tingles")/position = (90, 98)/txcolor = (0, 0, 0)/font = ("Calibri", -20, 700, 0, 49)/ items= ("Zeit = <% script.currenttime %>")/position = (4, 1)/txcolor = (0, 0, 0)/font = ("Calibri", -20, 700, 0, 49)/items = ("falsche Taste")/select = noreplace/position = (50, 3)/txcolor = (200, 0, 0)/fontstyle = ("Calibri", 2.50%, true, false, false, false, 5, 1)______________________________________________________________________________/inputdevice = keyboard/validresponse = (1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48, 49, 50, 51, 52, 53, 54, 55, 56, 57, 58, 59, 60, 61, 62, 63, 64, 65)/correctresponse = (30, 34, 38)/errormessage = true(error, 400)/branch = [trial.asmr_target_measure]____________________________________________________________________________ /preinstructions = (welcome, how_to1, how_to2, how_to3, instruction1, instruction2)/trials = [1=asmr_target_measure]/bgstim = (asmr_target, reminder_basline_left, reminder_relaxation_middle, reminder_tingling_right, current_time)/timeout = 1191000/postinstructions = (expt_end)/blocks = [1=preinstruction; 2=target; 3=postinstruction]_______________________________________________________________________________/screencolor = (0, 0, 0)/txcolor = (whitesmoke)__________________________________________________________ /txcolor = (255, 255, 255)/screencolor = (0, 0, 0)/fontstyle = ("Calibri", 3.00%, false, false, false, false, 5, 1)/nextkey = (" ")/prevkey = ("p")/nextlabel = "(Leertaste) nächste Seite..."/prevlabel = "(p) vorherige Seite..."The block object has the timeout. Initializing the block object takes time before it starts running the first trial, and it may take a different amount of time on different systems running at different refresh rates -- to draw a stimulus to the screen, Inquisit necessarily has to wait for the start of a dispaly refresh cylce. It cannot draw stimuli while the display is in the middle of a refresh cycle. Same with trial objects. Moreover, your trial has to display error messages for some responses, so that would not be reflected at all when you simply add up latencies. In short, you cannot and should not expect the individual latencies to neatly sum up to exactly the set timeout value.To illustratre the latter point about error message duration not being reflected in the latencies: #### Merge Selected

Merge into selected topic...

Merge into merge target...

Merge into a specific topic ID...