Skip to content

natusdir & Data Collection Files

What this page tells you

The pipeline needs three files: channel mapping (see Automated Channel Mapping), natusdir (tells natus2mef where raw files and output mefs go), and data collection (records real Natus start times). Copy natusdir and data collection from the example patient in ieeg_metadata; name them HUPXXX_natusdir, HUPXXX_CCEPS_natusdir, etc.

In order to run the EEG processing pipeline, you need 3 files: Channel Mapping, Natusdir, and Data Collection.

These files are:

  1. Channel Mapping
    1. Go to Automated Channel Mapping (Automated Channel Mapping)
  2. Natusdir
    1. This file is used to run the natus to mef conversion. It essentially will tell the code where to find all of the raw natus eeg files and then where to output the mefs.
    2. For the Natusdir files, please name them accordingly:
      1. HUPXXX_natusdir (for intracranial)
      2. HUPXXX_CCEPS_natusdir
      3. HUPXXX_Gottfried_natusdir
      4. HUPXXX_Gold_natusdir
  3. Data Collection
    1. This file is used to keep track of the actual start times, dates, and names of the eeg files in Natus, since this will all be date-shifted to 2000-01-01 when uploaded to ieeg.org
    2. For the data collection files, please name them accordingly:
      1. HUPXXX_datacollection (for intracranial)
      2. HUPXXX_CCEPS_datacollection
      3. HUPXXX_Gottfried_datacollection
      4. HUPXXX_Gold_datacollection

For the Natusdir and Data Collection files, you can copy them from the example patient (in ieeg_metadata) into the HUPXXX folder you are working with (in ieeg_raw), and then change the information inside to match your current patient.

Below is an example natusdir file:
HUP257 natusDir notepad; RID, implant/admission dates and folder names redacted with black boxes

Below is an example data collection file:
HUP257 data collection notepad; dates and times redacted, GUIDs and seizure labels visible