Center for Neuroengineering & Therapeutics (CNT)¶
The CNT is home to the Penn Epilepsy Center research groups of Erin Conrad, Kate Davis and Brian Litt. The lab and the CNT run the epilepsy data infrastructure together: the servers (cnt1, cnt-fs, the BSC allocation), the data, the coordinators, and the pipelines that take intracranial EEG and imaging from the epilepsy monitoring unit to analysable, de-identified datasets. The lab has a touchdown space at the CNT.
Procedures that both groups use are kept in both manuals and maintained together; each such page here carries a note and a link to the CNT's copy, and a change to a shared step is agreed with the CNT before either manual is edited. The CNT's own work, such as consenting, scanner-day and participant-facing coordinator procedures, lives only in the CNT procedures manual, maintained by the CNT associate director.
Procedures kept in both manuals¶
Data
- De-Identifying EDF Headers · De-identification
- De-Identifying EDFs · De-identification
- De-identifying NIfTI Headers · De-identification
- Data Storage Locations · Storage Locations
- Pennsieve Data Access Rules · Sharing (Pennsieve & ieeg.org)
- Uploading to Pennsieve Locally · Sharing (Pennsieve & ieeg.org)
- Uploading from cnt1 to Pennsieve · Sharing (Pennsieve & ieeg.org)
- Pennsieve Downloader · Sharing (Pennsieve & ieeg.org)
- Moving Data Across cnt-fs, cnt1, BSC, Borel & Leif · Moving Data
- Transferring Files from Box to cnt-fs (rclone) · Moving Data
- Archiving EEG Data to Azure · Archiving (Azure)
- cnt1 Scripts for Azure Archiving & Unarchiving · Archiving (Azure)
Compute
- Submitting Jobs with SLURM · SEAS (CETS) Servers
- Mounting Leif over SMB · SEAS (CETS) Servers
- SLURM on Finkel: Configuration & Limits · SEAS (CETS) Servers
- SEAS Servers: Borel, Leif, Pioneer · SEAS (CETS) Servers
- Accessing Borel over SSH · SEAS (CETS) Servers
- Submitting CETS & PMACS Helpdesk Tickets · Support & Tickets
- Overview of CNT Systems · Overview
- PMACS VPN · PMACS (PSOM) Systems
- BSC Cluster · PMACS (PSOM) Systems
Imaging
- RADAR Data Pulls · Clinical Imaging Pulls (RADAR)
- Grid Electrode Labeling Conventions · Electrode Reconstruction
- MUSC Reconstruction · Electrode Reconstruction
- Electrode Reconstruction: Prep & Software · Electrode Reconstruction
- GUI/Docker Reconstruction Workflow · Electrode Reconstruction
- DICOM → NIfTI (non-BIDS) · Formatting
Electrophysiology
- Automated Channel Mapping · Channel Mapping
- Channel Mapping for EDFs (ieeg-dataset.ini) · Channel Mapping
- The config Folder · Overview & Setup
- sEEG Phase II Processing: Overview & Timeline · Overview & Setup
- The ieeg.properties File · Overview & Setup
- natusdir & Data Collection Files · Overview & Setup
- Mounting cnt-fs · Overview & Setup
- Setup for Processing · Overview & Setup
- Troubleshooting Processing Errors · Processing & Upload to ieeg.org
- Final Step: Delete mef Folders · Processing & Upload to ieeg.org
- Anonymize & Upload EDFs to ieeg.org · Processing & Upload to ieeg.org
- Deleting a Dataset from ieeg.org · Processing & Upload to ieeg.org
- Adding an iEEG File to a Project · Processing & Upload to ieeg.org
- Splitting Datasets · Processing & Upload to ieeg.org
- Processing for ieeg.org (natus2mef → validate → upload) · Processing & Upload to ieeg.org
- Re-uploading Archived Datasets · Archiving on ieeg.org
- Archiving ieeg Files · Archiving on ieeg.org
- Unarchiving an ieeg Dataset · Archiving on ieeg.org
- Exporting Files from Natus · Exporting from Natus
REDCap & Clinical Metadata
- REDCap Tips · Projects & Data Entry
- Seizure Terminology Reference · Projects & Data Entry
- Surgical Outcomes REDCap Project · Projects & Data Entry
- RADAR Pull → REDCap Entry · Clinical Data Pulls (EHR → REDCap)
Operations
- Onboarding & Offboarding Checklist · Onboarding & Offboarding
- PennKey & REDCap Access for External Guests · Access & Accounts
- Adding Users to the ieeg.org Portal · Access & Accounts
- Requesting a REDCap Account · Access & Accounts
- Adding a Non-Penn / New Hire to a Study · Regulatory, IRB & Reporting
- Adding Personnel to an IRB Study · Regulatory, IRB & Reporting
Rules that apply on the shared systems¶
Identified data lives only on cnt1, cnt-fs and the BSC cluster, behind the PMACS VPN; nothing leaves them without the de-identification procedure for its type. Accounts are requested through the helpdesk procedure under the lab's sponsor and IRB; the data research coordinator files them.