Before, the triggering code always added all channels together. However, since different channels may be different devices, or once channel may be bad, it's useful to be able to customize this.
To do this, I've added a chan_to_trigger option to the OptimumFilt class in the triggering code. This allows the user to specify either 'all' for all channels, a single channel (e.g. 0), or multiple channels (e.g. [0, 2] for the first and third channels). I've also updated the continuous trigger demo (which uses some Stanford data), such that it specifies this keyword argument.
Before, the triggering code always added all channels together. However, since different channels may be different devices, or once channel may be bad, it's useful to be able to customize this.
To do this, I've added a
chan_to_triggeroption to theOptimumFiltclass in the triggering code. This allows the user to specify either'all'for all channels, a single channel (e.g.0), or multiple channels (e.g.[0, 2]for the first and third channels). I've also updated the continuous trigger demo (which uses some Stanford data), such that it specifies this keyword argument.