PipeCompare 0.8.0

Renamed: NeuroQC is now PipeCompare. This is an incompatible change:

• Package +neuroqc → +pipecompare, class NeuroQC → PipeCompare
  (pipecompare.PipeCompare.optimize, .adopt, …), eegplugin_pipecompare,
  pipecompare_setup.
• Error IDs PipeCompare:…; Command Window prefix [PipeCompare]; base variable
  pipecompare_result; menu tag pipecompare_menu; environment variable
  PIPECOMPARE_REAL_SET.
• New datasets carry EEG.etc.pipecompare, and history lines are tagged % PipeCompare.
• The segment event type is pipecompare_seg.

Compatibility.

• Datasets adopted with NeuroQC still work: a trial rule they carry under EEG.etc.neuroqc is
  cleared before a search, as the new field is, and their % NeuroQC history lines are still
  recognized as NeuroQC's own.
• Checkpoint folders written by NeuroQC 0.7 cannot be resumed (other class names and search
  identity); run those searches again.
• Install the plugin folder as PipeCompare (or PipeCompare0.8.0) under eeglab/plugins/,
  and remove the old NeuroQC folder, or both menus appear.

Added

• Simple mode: EEGLAB > Tools > PipeCompare > Compare pipelines… (pop_pipecompare). It takes three
  choices: data type, a measure (ERP CORE component presets or a frequency band), and a recipe
  (filters, standard, full). It shows a live pipeline count, a result window, and an
  EEGLAB-style command in ALLCOM. The panel becomes Advanced panel….
• Band power for continuous data (e.g. resting state):
  Contract('analysis', 'bandpower', 'segment', T, 'bands', ...). Segments are marked with
  eeg_regepochs and paired by urevent. The score is log10 band power (Hann taper), and the
  signal check uses a sinusoid at the band centre. Dependent segments are compared with a
  moving-block bootstrap. Event-related band power is available with conditions + epoch.
  ERP results are unchanged.