lvanderlinden
About
- Username
- lvanderlinden
- Joined
- Visits
- 1,620
- Last Active
- Roles
- Administrator
Comments
-
Hi Boo, I'm glad to hear the block feedback works fine now! Trial feedback: Regarding the trial feedback, you say that you placed the reset_feedback item as in the 'Extended template', that is, at the start of the block_sequence. However, if you …
-
Hi Boo, Welcome to the forum and thank you for your interest in OpenSesame! * Regarding your first question, I would suggest deticking the "Reset feedback variables" box in your trial feedback item. If this box is ticked the feedback var…
-
Hi Vineeta, I'm glad that it's solved! Don't hesitate to ask any further questions! Regards, Lotje
-
Hi Vineeta, To start with, you could check the value in the Repeat box in your loop item(s). Perhaps your experimental loop starts over again because the Repeat value is higher than 1? If this doesn't solve your problem you could provide us with s…
-
Hi Michel, If I understand your question correctly, you want to * calculate a new accuracy score from the changed 'correct' variable * calculate a new average RT from the RT's on go-trials only This can be achieved by storing the appropriate vari…
-
Hi Samira, Glad to hear you like OpenSesame! To show a feedback item solely if a participant responded too slow, you could use a "Run if" statement (see http://osdoc.cogsci.nl/usage/variables-and-conditional-qifq-statements) to determine…
-
Hi Sayb, I'm glad it worked! Please let us know if you have any further questions. Cheers, Lotje
-
Hi Sylvia, Thanks for your post! It turns out that indeed response variables set in forms are not (always) detected automatically by the logger item. Sebastiaan fixed this for the next update! So one thing you could do is to download the latest pre…
-
Hi, Is there a specific reason for having different loggers for the different loops? If not, I would suggest using the same logger item at the end of each loop. This can be achieved as follows: * Make a logger item for your first sequence (by clic…
-
Hi George, Did you place the suggested Python code in the "Run phase" tab of your inline_script item? The variable avg_rt is calculated during the run phase of a sequence, so if the code is placed in the "Prepare phase" tab it w…
-
EDIT: The new variable should not be called "run", because a built-in variable named "run" already exists. (See posts below.) Hi George, Thanks for your post! You discovered a bug which Sebastiaan plans to fix for the next vers…
-
Hi Sylvia, Firstly, I would recommend to download the latest pre-release (pre11), because the form functionality was updated today (30-09-2012). With regard to your question, the forms do not contain built-in functionality for this yet (although i…
-
About local and global variables I just want to add something about accessing variables that are defined in the interface. With the exception of variables defined in a loop item, all variables that are set via the interface are local, meaning that…
-
Hi Anthony, That's just because 3 times 0.33 is 0.99. More specifically, the number of cycles that is actually executed is always the floor of the input number. The floor of 0.99 is 0. Therefore, if you set the repeat to 0.34 (0.34 * 3 = 1.02), …
-
Hi Kyle, With the second version of your script you're almost there! The only thing is that you should place a logger item at the end of every sequence instead of only at the very end of your experiment. By doing this, every trial/question looks as…
-
ITA Hi Kyle, I'll get back to you soon! Regard
-
Hi Aaron, Yes, that's certainly possible. You can use the Python module 'time' for this: * http://docs.python.org/library/time.html If you read this documentation you can figure out what kind of time stamp is most appropriate for your purpose. T…
-
Hi Frank, If you simply cut-and-past your script in "Prepare_Trial" to the prepare instead of the run phase your problem is solved. This is because the prepare routine of each item in a sequence is called before the run routine. * A sket…
-
Hi Sarah, I think if you make the following changes your experiment will be good-to-go: * You can assign a random integer (number without decimals) between 800 and 2000 to the variable random820 by using the Python module random. In an inline scri…
-
Hi Christiane, I would recommend to structure your trial sequence as follows: * Present the visual stimulus with a duration of 2000 ms. * Present the auditory stimulus with a duration of 1000 ms. This will give the desired result because a sample…
-
Hi Christiane, Yes, that's certainly possible! The best way to do this is: * by selecting the pictures from a loop item (and set the sequence to 'sequential') * and by selecting sounds with an inline script. I attached an example experiment to de…
-
Hi Johannes, Thanks for your email and explanation! First off, the failure of test script cannot be related to the fact that only trigger changes are recognised because this is exactly what the test script does: looping through a range of triggers…
-
Hi Kyle, I'm glad it helped! With regard to the empty output file: I think you didn't place a logger item at the end of your trial sequence. Could that be it? (If you don't append a logger item OpenSesame does store all experimental variables but …
-
Hi Kyle, For the first part of your experiment (the semantic questions) I recommend you'd use the questionnaire plug-in, which can be downloaded from here: * http://osdoc.cogsci.nl/plug-ins/41-questionnaire-plugins For the second part of your exp…
-
Hi Johannes, It's no problem at all to ask a lot of questions! On the contrary; that's what the forum is for! Our discussions could be informative for others and at the same time your information is very helpful for the documentation on OpenSesame…
-
Update: On a general note I would like to add that communicating about variables between the GUI and Python inline code works very easily and as follows: * To get an in a loop defined variable in an inline_script, use: self.get("var"…
-
Dear Guido, I think the simplest way to achieve your goal is, in fact, via the interface rather than an inline script. This is because you can easily paste the content of your .csv file into a loop item in the following way: * Create a loop item a…
-
Hi Johannes, Thank you for sending us your experiment. Your code looks very good and it took us a while to find out what could be causing the unintended triggers. But I think we found it. The function DlPortWritePortUchar(), which is not a native …
-
Hi, Could it be the case that the duration of the item just before the keyboard_response item (e.g. a sketchpad) is still set to "keypress"? In this case, a first keypress is needed to advance the experiment to the next item (the keyboard…
-
Hi Johannes, With regard to your first question, OpenSesame does not generate triggers automatically. This should therefore be caused by something in one of your inline scripts. It's difficult for me to tell where in your code the additional trigge…