Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • bids_lossless_eeg bids_lossless_eeg
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • bucanl_pipelines
  • bids_lossless_eegbids_lossless_eeg
  • Wiki
  • qc main

Last edited by Tyler Collins Oct 03, 2018
Page history

qc main

Quality Control - Main Procedure

Once files have completed a quality control (QC) initialization procedure, they can be loaded via a Batch Context QC script. This script allows for interactive annotation of files, and the exporting of this state after expert review.

The following sections introduce how to load files into the main QC script, use of the QC interface, and suggested decision making criteria.

Loading Files into Quality Control

Initially, the vised configuration for the QC procedure must be loaded. Begin by navigating Matlab to the root directory of the project, and adding the code folder to the path via addpath('code') in the command window. Next, in the command window run eeg_init_path followed by eeglab. You should be presented with the typical eeglab interface. Using the menu bar navigate to File -> Vised Configuration. You should be presented with the following interface: visedConf Click Load vised config and navigate the file chooser to derivatives/lossless/code/config and select the file vised_config_qc.cfg. The above interface should now be populated with values. Click OK to proceed.

Next, the history template batch (htb) menu is used to launch the main QC procedure. Use the menu bar to navigate to File -> Batch -> Run history template batch. An unpopulated version of the below interface should now be shown. Load the qc.htb script by clicking History file and navigating to derivatives/lossless/code/scripts and selecting the qc.htb file. To select a file to QC, click Data file import and navigate to the file of your choice.

Note: These files should have the "qc" suffix signaling they have completed QC initialization. Note: Copy and pasting paths relative to the root of the project allows for multiple files to be QC'd in a single execution.

The following image shows a completed htb interface to run three face13 files through the main QC procedure: qcMain

By clicking OK, the QC procedure will be run on selected files.

Manipulating Files During Quality Control

Need reference from Mike and James

Decision Making Criteria

Under construction.

Clone repository
  • assumptions
  • bidsifying
  • configuring context config
  • configuring remote
  • contributing
  • developer workflow
  • directories
  • essinit
  • Home
  • init scripts
  • install download
  • opening eeglab
  • pipeline scripts
  • postprocessingscript
  • qc init
View All Pages