[Eeglablist] Importing events from NBS presentation
Shannon Proksch
Shannon.Proksch at augie.edu
Tue Oct 1 11:55:36 PDT 2024
Hello,
I am working on importing events from NBS Presentation to EEG data which
were recorded with ANT Neuro's eego software. We are using the Cedrus C-pod
to send events from Presentation to the EEG during recording.
The C-pod only emulates a serial port, so cannot send truly event-related
'triggers'. We are sending a port code (event) to the EEG at the start of
the scenario, and another port code (event) to the EEG after the first
button response after the instructions. Only this second event is recorded
as a response in the Presentation log file.
Using the Importing events from a Presentation file
<https://urldefense.com/v3/__https://eeglab.org/tutorials/04_Import/Importing_Event_Epoch_Info.html*:*:text=removing*2Frenaming*20events-,Importing*20events,Import*20event*20info*20menu*20item__;I34lJSUlJSUl!!Mih3wA!CmnCEQFLXRcUEcO7dRtfp5pzEcDZxQsFx5rexU5fqz-sklFi5DLbO1sPWUhrF7YKPDM4XSSUH_cHOZoH_nhyKxt36APMTCMDXA$ .>tool
in EEG lab, is there any way to sync the Presentation log file to that *second
*port code (event) that is recorded in my EEG data? Or will it only
automatically sync to the first port code, which is technically the first
event shown in the EEG signal?
Thanks for any help. Please let me know if there is more information that
would be helpful for answering this question. (Or if any one happens to
have tips for using Presentation and Cedrus c-pod together for auditory
stimulus/response time experiments that would help me before I get to the
eeglab stage.)
Relevant info from the NBS Presentation help forum, when I asked how to
send event-related triggers to the EEG, is below:
> > There are two ways to send port output in Presentation:
> >
> > 1. Event-related output. In this case, the port output is bound to an
> event occurrence, and is what you would generally think of as 'triggers'.
> Generally speaking, you assign a port code value to some stimulus event,
> and any time that stimulus event happens, a trigger is sent at the same
> time. Event-related output of this sort can only be done with a parallel
> port, or a device that emulates a parallel port.
> >
> > 2. "Manual" output. In this case, port output is not linked to an event
> onset; instead, you are putting a line (or lines) in your script to send a
> code (i.e., using output_port::send_code(), as in the demo script for the
> c-pod). When using manual output, events and triggers are not, and cannot
> be, bound together. They must occur sequentially (i.e., you can present a
> stimulus and then send a code, which means the stimulus and the code will
> occur *close together* in time, but not be bound).
> >
> > The c-pod emulates a serial port, and moreover has some unique
> requirements for how codes are structured. As a consequence, it requires
> the use of 'manual' output (option 2 above). Unfortunately the ERP CORE
> experiments are designed for (and in some senses, should require)
> event-related output (option 1). There is not really any way to rework
> those experiments to use manual port output. We have been looking into
> whether there is a way for the c-pod to be re-configured so that it can
> send event-related output, and I will let you know if we make any headway
> on that. But currently there is no way to do event-related output with the
> c-pod.
Take care,
-Shannon
Shannon Proksch, PhD
Assistant Professor, Psychology & Neuroscience
https://urldefense.com/v3/__http://www.shannonproksch.com__;!!Mih3wA!CmnCEQFLXRcUEcO7dRtfp5pzEcDZxQsFx5rexU5fqz-sklFi5DLbO1sPWUhrF7YKPDM4XSSUH_cHOZoH_nhyKxt36APjNkrqbA$
Pronouns: she / her <https://urldefense.com/v3/__https://en.pronouns.page/she__;!!Mih3wA!CmnCEQFLXRcUEcO7dRtfp5pzEcDZxQsFx5rexU5fqz-sklFi5DLbO1sPWUhrF7YKPDM4XSSUH_cHOZoH_nhyKxt36APgPivwRA$ >
Augustana University
2001 South Summit Avenue,
Sioux Falls, SD 57197 | https://urldefense.com/v3/__http://www.augie.edu__;!!Mih3wA!CmnCEQFLXRcUEcO7dRtfp5pzEcDZxQsFx5rexU5fqz-sklFi5DLbO1sPWUhrF7YKPDM4XSSUH_cHOZoH_nhyKxt36APpa3m95Q$
More information about the eeglablist
mailing list