This README.txt file was generated on <20200611> by Alireza Chamanzar # # General instructions for completing README: # For sections that are non-applicable, mark as N/A (do not delete any sections). # Please leave all commented sections in README (do not delete any text). # ------------------- GENERAL INFORMATION ------------------- 1. Title of Dataset: Pediatric patients with lobectomy (MRI and EEG) This dataset includes structural MRI and EEG raw data related to the paper entitled Chamanzar, Behrmann, and Grover (2020), where we have proposed the SilenceMap algorithm to localize neural silences using noninvasive scalp EEG. The link to our paper will be made available as soon as it is published online. Our SilenceMap software is available here: Chaman Zar, Alireza; Behrmann, Marlene; Grover, Pulkit (2020): SilenceMap: open source codes and software. Carnegie Mellon University. Software. https://doi.org/10.1184/R1/12402413 # # Authors: Include contact information for at least the # first author and corresponding author (if not the same), # specifically email address, phone number (optional, but preferred), and institution. # Contact information for all authors is preferred. # 2. Author Information First/Corresponding Author Contact Information Name: Alireza Chamanzar Institution: Carnegie Mellon University Address: Hamerschlag Hall B200, 5000 Forbes Ave., Pittsburgh PA 15213 United States Email: achamanz@andrew.cmu.edu Phone Number: n/a Second/Corresponding Author Contact Information Name: Marlene Behrmann Institution: Carnegie Mellon University Address: 331 Baker Hall, 5000 Forbes Ave., Pittsburgh PA 15213 United States Email: behrmann@cmu.edu Phone Number: n/a Third/Corresponding Author Contact Information Name: Pulkit Grover Institution: Carnegie Mellon University Address: Hamerschlag Hall B202, 5000 Forbes Ave., Pittsburgh PA 15213 United States Email: pgrover@andrew.cmu.edu Phone Number: n/a --------------------- DATA & FILE OVERVIEW --------------------- # # Directory of Files in Dataset: List and define the different # files included in the dataset. This serves as its table of # contents. # Directory of Files: MRI_dataset/ UD_defaced.nii.gz -> anonymized structural MRI scan of patient UD with right occipitotemporal lobectomy OT_defaced.nii.gz -> anonymized structural MRI scan of patient OT with left temporal lobectomy SN_defaced.nii.gz -> anonymized structural MRI scan of patient SN with left temporal lobectomy EEG_Dataset/ (use EEGLAB toolbox to read these bdf files) UD/ -> a folder containing all EEG/ECG/EOG recording of patient UD, including different visual recordings (SSVEP_L, SSVEP_R) OT/ -> a folder containing all EEG/ECG/EOG recording of patient OT, including different visual recordings (SSVEP, SSVEP_L, SSVEP_R) SN/ -> a folder containing all EEG/ECG/EOG recording of patient SN, including different visual recordings (SSVEP, SSVEP_L, SSVEP_R) DH/ -> a folder containing all EEG/ECG/EOG recording of a healthy participant DH, including visual recordings (SSVEP) EEG_Stimuli/ -> a folder containing all of the matlab codes for the visual stimuli of the EEG recording in this dataset. vis_SSVEP.m -> matlab code for the SSVEP stimulation vis_SSVEP_L.m -> matlab code for the left SSVEP stimulation vis_SSVEP_R.m -> matlab code for the right SSVEP stimulation maskandtest_m1.mat -> matlab file containing the SSVEP patterns used in vis_SSVEP.m, vis_SSVEP_L.m, and vis_SSVEP_R.m. maskandtest_m2.mat -> matlab file containing the SSVEP patterns used in vis_SSVEP.m, vis_SSVEP_L.m, and vis_SSVEP_R.m. EEG experiment protocol_KiltHub.pdf -> a document which explains the details of the visual stimuli, trial structures, and instruction on how to use the stimuli matlab codes. Additional Notes on File Relationships, Context, or Content (for example, if a user wants to reuse and/or cite your data, what information would you want them to know?): # # File Naming Convention: Define your File Naming Convention # (FNC), the framework used for naming your files systematically # to describe what they contain, which could be combined with the # Directory of Files. # File Naming Convention: We have used a unique code for each participant's name to protect the identity of our participants from being discovered by others. # # Data Description: A data description, dictionary, or codebook # defines the variables and abbreviations used in a dataset. This # information can be included in the README file, in a separate # file, or as part of the data file. If it is in a separate file # or in the data file, explain where this information is located # and ensure that it is accessible without specialized software. # (We recommend using plain text files or tabular plain text CSV # files exported from spreadsheet software.) # ----------------------------------------- DATA DESCRIPTION FOR: N/A ----------------------------------------- 1. Number of variables: 2. Number of cases/rows: 3. Missing data codes: Code/symbol Definition Code/symbol Definition 4. Variable List # # Example. Name: Gender # Description: Gender of respondent # 1 = Male # 2 = Female # 3 = Transgender # 4 = Nonbinary # 5 = Other gender not listed # 6 = Prefer not to answer # A. Name: Description: Value labels if appropriate B. Name: Description: Value labels if appropriate -------------------------- METHODOLOGICAL INFORMATION -------------------------- # # Software: If specialized software(s) generated your data or # are necessary to interpret it, please provide for each (if # applicable): software name, version, system requirements, # and developer. #If you developed the software, please provide (if applicable): #A copy of the software’s binary executable compatible with the system requirements described above. #A source snapshot or distribution if the source code is not stored in a publicly available online repository. #All software source components, including pointers to source(s) for third-party components (if any) 1. Software-specific information: Name: Version: System Requirements: Open Source? (Y/N): (if available and applicable) Executable URL: Source Repository URL: Developer: Product URL: Software source components: Additional Notes(such as, will this software not run on certain operating systems?): Our SilenceMap software is available here: Chaman Zar, Alireza; Behrmann, Marlene; Grover, Pulkit (2020): SilenceMap: open source codes and software. Carnegie Mellon University. Software. https://doi.org/10.1184/R1/12402413 # # Equipment: If specialized equipment generated your data, # please provide for each (if applicable): equipment name, # manufacturer, model, and calibration information. Be sure # to include specialized file format information in the data # dictionary. # 2. Equipment-specific information: N/A Manufacturer: Model: (if applicable) Embedded Software / Firmware Name: Embedded Software / Firmware Version: Additional Notes: # # Dates of Data Collection: List the dates and/or times of # data collection. # 3. Date of data collection (single date, range, approximate date) : Nov 2018-Nov 2019