The psychopathic ISI component and how to use it to load incentives into Builder
I have some doubts if I understand the concept of a static component correctly or not.
I am designing an experiment in which I present images for specific periods of time, and once the image is gone, the participant will have to submit a response.
I use a builder for this, and usually at the end I go to the encoder view to make some minor changes (random intermediate durations, etc.)
So, in the builder, I run a loop where my first subroutine has an ISI component for 0.5 seconds, then I add an image declaration for 0.5 seconds, the second procedure in the loop writes the key's response.
What I want to do to avoid lag is load the image during ISI and then display it after 0.5 seconds has passed. I am fine with the condition file and how to use the parameters as variables. So in the Image post I am using $ image (as stated in my excel file), I also state that I want this image to be installed "during trial: ISI". Does this do what I mean? Load the image during ISI and flip it after ISI is complete?
Secondly, do you think it would be more efficient to have ISI and image in different procedures within the same cycle?
If you have any other suggestions on how this can be done in a more efficient way, please let me know.
Thank.
source to share
(1) Yes, this is the correct way to use ISI to preload an image.
(2) No, there is no need to separate different subroutines.
(3) You should avoid going "to view the encoder to make some minor changes". When you make changes, the Builder view can no longer be used. It is very likely that you can achieve what you want by putting the code in the code component in the Builder view, so you don't have to give up the benefits of the GUI.
source to share