By default we have average=False in compute_proj_ecg and compute_proj_eog. But when I was toying with the idea of using Xdawn (which I think might still be a good idea) to compute projectors rather than plain SSP, I found that average=True seemed to always be better than average=False.
Here is the sample data, with four columns: the first two are average=False, the last two are average=True; within those, the left are ECG epochs (to be projected) and the right are auditory epochs (hopefully not contaminated):

Note that the "average=True" does not really make sense for Xdawn because it already uses the average, so the first two and last two columns are the same for Xdawn.
I think we might consider:
By default we have
average=Falseincompute_proj_ecgandcompute_proj_eog. But when I was toying with the idea of usingXdawn(which I think might still be a good idea) to compute projectors rather than plain SSP, I found thataverage=Trueseemed to always be better thanaverage=False.Here is the sample data, with four columns: the first two are
average=False, the last two areaverage=True; within those, the left are ECG epochs (to be projected) and the right are auditory epochs (hopefully not contaminated):Note that the "average=True" does not really make sense for Xdawn because it already uses the average, so the first two and last two columns are the same for Xdawn.
I think we might consider:
average=Falsetoaverage=True.Probably unifycompute_exg_projandcreate_exg_epochs. The former does not use the latter but it probably should.average=Trueit should do better against other noise present in the epochs, especially if that noise is large (yet to be shown).