[Eeglablist] Editing Events, Exporting, Importing

[Cedric Cannard]

Dear Royce and Connor,

It is hard to follow the details by email descriptions to really understand the problem.

- I'm not familiar with this MFF data type, but am familiar with the Biosig toolbox. You could send me your file and I can take a look if you want.
- have you tried the different importing options of the Biosig pop-up window? People have reported event problems being solved by simply unchecking/checking some of these options.
- note: to avoid redoing processing manually again, you can type eegh in your command window after each step (or at the end of your steps), and EEGLAB will print all the command lines corresponding to what you did manually in the GUI (even bad samples rejected manually). You can then read them and apply all these steps automatically, which shouldn't take too long.

Cedric

------- Original Message -------
On Sunday, January 29th, 2023 at 9:43 PM, Lee, Royce [BSD] <rlee1 at bsd.uchicago.edu> wrote:

> Thank you Connor. Yes, the data were imported into EEGlab using the Biosig Plugin. Today I reviewed the EEGlab wiki carefully, paying close attention to the parameters and the example spreadsheet. I believe I have identified the reason why using this specific .set file, I’m having difficulty export a trigger .txt file and importing the same file. This .set file has been artifact rejected and has undergone ICA. Because we spent time on this process, we would rather not redo previous step of importing. This specific file outputs a .txt file with about 8 – 9 headers on the first line. Far more complex than the example in the wiki and that I’ve seen using our previous Biosemi recordings. However, the boundary events created by EEGlab 2022.1 (with Boundary event = -99) have only three headers: time, trigger type (boundary), and number (sequential numbered triggers). Thus, the .txt file has a combination of two different schemes, and the boundary and trigger roles are interleaved. It does not make sense on the page, and I’m guessing that if I had one or the other, the export-import process via the GUI would work smoothly.
>
> So, I think what we’ll do is write python code to take the complex trigger file and simplify/standardize it to a simpler format with three columns. I’ll report back if this works. If it does, the next step will be to edit the trigger files with conditional triggers, which should resolve the confusing and non-specific trigger scheme the data wound up using. Specifically, the only way to know if an emotional face stimuli are of a certain valence is if that stimulus is paired with a fixation cross that is encoded with the value of the emotional valence of the entire block of stimuli (fixation point, schematic face, emotional face).
>
> I understand this may be possible in Matlab, but I don’t yet have the ability to write this code.
>
> Royce Lee
>
> From: Connor Haggarty <chaggarty at uchicago.edu>
> Sent: Sunday, January 29, 2023 4:31 PM
> To: Cedric Cannard <ccannard at protonmail.com>; Lee, Royce [BSD] <rlee1 at bsd.uchicago.edu>; eeglablist at sccn.ucsd.edu
> Subject: Re: [Eeglablist] Editing Events, Exporting, Importing
>
> MFF using EGI.
>
> We have had three options from them. Segment in their own software meaning going back to the start of processing. To import into matlab using just trigger codes meaning going back to the start. Or manually changing the triggers in the event list so we are trying the latter
>
> Connor (Royce’s colleague)
>
> ---------------------------------------------------------------
>
> From: eeglablist <eeglablist-bounces at sccn.ucsd.edu> on behalf of Cedric Cannard via eeglablist <eeglablist at sccn.ucsd.edu>
> Sent: Sunday, January 29, 2023 3:32:04 PM
> To: rlee1 at bsd.uchicago.edu <rlee1 at bsd.uchicago.edu>; eeglablist at sccn.ucsd.edu <eeglablist at sccn.ucsd.edu>
> Subject: Re: [Eeglablist] Editing Events, Exporting, Importing
>
> Dear Royce,
>
> What data type (and recorded by what EEG system) are you referring to?
>
> Cedric
>
> On Sun, Jan 29, 2023 at 09:56, Lee, Royce [BSD] <rlee1 at bsd.uchicago.edu> wrote:
>
>> Hello list,
>>
>> We have an experiment in which we are interested analyzing the ERPs to various face stimuli. It seems that importing the data into EEGlab has caused some problems with the trigger labels. We have exported the trigger information in a text file and generated some Python code to correct the trigger labels. Using the conditional triggers (the current trigger n is depending on the specific value of n-1 or n-2 trigger), the code will correct the trigger labels.
>>
>> The problem I'm having seems to be quite basic. I had assumed that if I export the trigger data into a text file, edit that file with Python, and then import the data, the problem would be mostly solved. However, importing the data leads to various errors.
>>
>> As an experiment, I simply exported the event data data and re-imported it. This did not work either. I see on the wiki the pop_expevents code and the link to github but am not sure if this will work with the above workflow of exporting, editing, and then re-importing.
>>
>> Royce Lee
>>
>> _______________________________________________
>> Eeglablist page: [http://sccn.ucsd.edu/eeglab/eeglabmail.html](https://urldefense.com/v3/__http:/sccn.ucsd.edu/eeglab/eeglabmail.html__;!!MvNZe7V6M35iZPhbgng-hfU!ygoirpqPjqi9nAnd0kX3CRG1F6UD-D1UG7RiRiugrx4ZVPHxtNV0hVzNuRdiIZ2SuQ5z8FyrvkLJ-vacbD_UZf0UJb1O$)
>> To unsubscribe, send an empty email to eeglablist-unsubscribe at sccn.ucsd.edu
>> For digest mode, send an email with the subject "set digest mime" to eeglablist-request at sccn.ucsd.edu
> _______________________________________________
> Eeglablist page: [http://sccn.ucsd.edu/eeglab/eeglabmail.html](https://urldefense.com/v3/__http:/sccn.ucsd.edu/eeglab/eeglabmail.html__;!!MvNZe7V6M35iZPhbgng-hfU!ygoirpqPjqi9nAnd0kX3CRG1F6UD-D1UG7RiRiugrx4ZVPHxtNV0hVzNuRdiIZ2SuQ5z8FyrvkLJ-vacbD_UZf0UJb1O$)
> To unsubscribe, send an empty email to eeglablist-unsubscribe at sccn.ucsd.edu
> For digest mode, send an email with the subject "set digest mime" to eeglablist-request at sccn.ucsd.edu