INFO: Response Data Omitted from .edat file when using multiple input masks [18007]

This article applies to:

E-Prime 2.0

 

Detail
This article applies to experiments in which the following characteristics are present:

• The object collecting the response has multiple Input Masks (i.e., there is more than one device listed in the Duration/Input tab of the object's Properties pages).
• The Input Masks have their End Action property set to 'none' (versus 'Jump' or 'Terminate').
• The object collecting the response has extended input (i.e., there is an Input Mask 'TimeLimit' property which lasts longer than the object's Duration) and/or is using PreRelease.

Anytime an Input Mask accepts a response or times out, it updates the properties of the running object (RT, RTTime, ACC, etc) accordingly. Typically, when a mask completes, the other masks are terminated. However, in the above condition(s), the completion of one Input Mask does not terminate the others; when they time out, they are actually overwriting the properties of a previous response.

To get around this, you will need to configure the additional Input Mask so that it emulates the other. For example, if you have the Keyboard and SRBox listed as Input Masks on the same object, you would configure the SRBox to emulate the Keyboard. To do so, you will need to open the Experiment object and click the Devices tab. Select the SRBox and click the Edit button. In the Emulate Device property, you want to select the Keyboard. Thus, the subject will be able respond using the Keyboard or the SRBox, and responses from either device will be accepted and logged in the data file. Also, setting the SRBox to emulate the Keyboard also will allow the experiment to run even if the SRBox is not attached. For example, if you would need to share this .es file with a colleague who does not have an SRBox, he or she would still be able to run it since the SRBox is emulating the Keyboard device. Note that, when emulating a device, all responses must be valid for the device which is being emulated. For example, if you have the Keyboard emulate the Mouse, response such as F, W, or {SPACE} will not be valid, and will be recorded in the data file as if there were no response.

Configuring the SRBox to emulate another device will not affect its timing accuracy. The SRBox will still run with a zero debounce period and therefore be more accurate even though it is emulating another device.


Legacy End User Comments

David McFarlane 12/17/2012 16:49

See also KB 1176. Apparently, EP2.0.1.93 changes this behavior so that it acts in the expected way (extended input mask that completes disarms other input masks on the object).

If you wish to continue the discussion, please add a comment below!