Open scott-huberty opened 11 months ago
I can see use cases for it. One probably easy way to get this is to have remove_dc start working like picks does elsewhere (can be "all", list of int, etc.) and leave False and True as convenience wrappers for what they do now (basically empty list and "data", respectively I think).
Unclear if we should change the default to "all", though. Probably safest to leave it as is.
My gut feeling is that we don't use the browser to inspect an exact Y-value but rather Y-range and shape. The scaling which defines the range is centered and thus the browser also expects centered data. Thus, DC-offset correction, or rather centering, seems fine.
Since remove_dc
works per visible page (I think!), I can imagine that for certain signals (maybe eyetracking), DC removal would have a negative impact if the offset actually carries information. Do you have an example where this is indeed relevant @scott-huberty?
Oh you are right that it's already available! I did not notice. Then +1 to change the behavior as proposed.
That's an interesting point @cbrnr , in theory I could see that causing weird behavior but I don't have a concrete example with any data, no!
This came up in the discourse channel regarding Eyetracking channels, but could be relevant to any non electrophysiology channels.
The question being: should
remove_dc
only apply to electrophysiology channels?I think the general feeling is yes? If so, does
remove_dc
serve a double purpose of mean centering traces on the plot, and will removing it cause traces for some data to go beyond the current y-axis scalings?Cc @mscheltienne @britta-wstnr @sappelhoff