@@ -462,11 +462,33 @@ For multiple-epoch data, the scalp map obtained for the
462
462
different epochs is the same for a particular component. Is this normal
463
463
or is there some mistake that's being done in the analysis?
464
464
** Answer:** Because the ICA algorithm is applied in the electrode space
465
- domain, the same scalp maps are returned for all epochs. However the
465
+ domain, the same scalp maps are returned for all epochs. However, the
466
466
time course of one ICA component is different for each epoch (if its
467
467
activation value is 0 at a given time, it means that this component is
468
468
not expressed in the data at that particular time).
469
469
470
+ ### ICA activity warning
471
+
472
+ If you re-reference the data after running ICA, or if you remove channels, you might see the warning message:
473
+
474
+ ```
475
+ ICA activity do not match ICA weights, see ...
476
+ ```
477
+ As a rule of thumb, never perform a lossy re-referencing or channel
478
+ removal after running ICA. Instead, remove the channel or re-reference the data, then run ICA again.
479
+
480
+ When the data is referenced or if channels are removed, ICA scalp topographies are also referenced, and ICA activity remains unchanged.
481
+ However, the ICA assumptions are broken. In other words, we no longer have ICA_activations = ICA_weights * EEG_data.
482
+ Nevertheless, we believe this type of broken representation is the closest to the one available before re-referencing or removing
483
+ channel(s). The alternative, which consists of recomputing activities, is not ideal because it is no longer an ICA decomposition.
484
+ Importantly, if you save and reload the data, ICA activations are not saved by default, so EEGLAB will recompute them using
485
+ ICA weights and data. This is no longer a standard ICA decomposition. If is important for you to retain the ICA activities, we
486
+ advise that you save the data from the command line using
487
+
488
+ ```
489
+ save('-mat', 'EEG_dataset_with_ica.set', '-struct', 'EEG');
490
+ ```
491
+
470
492
Time Frequency
471
493
--------------
472
494
0 commit comments