[Eeglablist] Adding user data to the EEG structure

[Iversen, John]

John,

By convention, and to keep the EEG structure itself clean, it's common practice to put additional information as a subfield of

EEG.etc

E.g.

EEG.etc.myextradata

Many current plugins will use this location. You can of course do whatever you want with your own data, but if you plan to share the data it might be worth considering.

As a general rule, if you are storing a lot of data, you might consider Tarik's suggestion and store such data in a separate file, and e.g. store the path to that file in the EEG.etc structure. The reason for this is to keep the EEG structure as lightweight as possible. This is what is done by default for the EEG data itself, which is stored in a separate file. There are some contexts (large studies, or if you just want to take a look at IC weights or dipole fits or events) in which the option to only load the '.set' file header information is used. This is much faster--as long as it doesn't get loaded down with too much extra data. Again, only relevant if you plan to develop a plugin for general use, or share your data.

John



On Aug 5, 2018, at 4:37 PM, Johnson, John T. <john.johnson at gatech.edu<mailto:john.johnson at gatech.edu>> wrote:

Thanks Tarik!
I’ve tried having my own matrix of data, doing lookups, etc. but it’s a pain to maintain. (Essentially a DIY relational database.)
I’ll just tack my info onto the EEG struct.

Thanks,
John

John T. Johnson
PhD Student - Applied Physiology
Georgia Institute of Technology
john.johnson at gatech.edu<mailto:john.johnson at gatech.edu>

via Newton Mail<https://cloudmagic.com/k/d/mailapp?ct=dx&cv=9.8.421&pv=10.13.6&source=email_footer_2>

On Sun, Aug 5, 2018 at 7:24 PM, Tarik S Bel-Bahar <tarikbelbahar at gmail.com<mailto:tarikbelbahar at gmail.com>> wrote:
Hello,

One way to this is add one or more fields with that data to the EEG structure for each .set file, containing any data you wish. For example,

EEG.myextradata= myextradata;

Saving the file and other manipulations with eeglab functions should not affect the extra data.

Another way is to update the .set file information, which has some fields.

Another method is to build your own matrix of info across all subjects, and call as necessary for single-subject and group level analyses.

For core and other info, eeglab scripting tutorial and googling eeglablist for similar questions can help.




On Sun, Aug 5, 2018, 3:21 AM Johnson, John T. <john.johnson at gatech.edu<mailto:john.johnson at gatech.edu>> wrote:
Where is the best place to store my own data related to the EEG dataset?
And will it be treated as part of the dataset throughout manipulations in the GUI and pop_*, eeg_* functions?

Thanks,
John


via Newton Mail<https://cloudmagic.com/k/d/mailapp?ct=dx&cv=9.8.421&pv=10.13.6&source=email_footer_2>
_______________________________________________
Eeglablist page: http://sccn.ucsd.edu/eeglab/eeglabmail.html
To unsubscribe, send an empty email to eeglablist-unsubscribe at sccn.ucsd.edu<mailto: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<mailto:eeglablist-request at sccn.ucsd.edu>
_______________________________________________
Eeglablist page: http://sccn.ucsd.edu/eeglab/eeglabmail.html
To unsubscribe, send an empty email to eeglablist-unsubscribe at sccn.ucsd.edu<mailto: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<mailto:eeglablist-request at sccn.ucsd.edu>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://sccn.ucsd.edu/pipermail/eeglablist/attachments/20180806/593de51d/attachment.html>