-
Notifications
You must be signed in to change notification settings - Fork 180
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The filter bank paradigm does not correspond to the new abstraction that depends only on the MNE #668
Comments
@bruAristimunha do you have a bit more details? like a bit of code First thought that comes to mind: could this be related to edge effects while filtering on epoched data? |
Thanks for replying @PierreGtch, I was thinking about it while looking at the code, and you're right. We have two things here: if we have a paradigm that creates filters correctly, e.g, if we pass the frequency list, we create a bank on the data as a whole. moabb/moabb/paradigms/motor_imagery.py Lines 158 to 167 in d2edb29
And we have a mixer/function that filters the data that has already been epoched, applying the filter at training time, which doesn't necessarily use mne to filter. In my experience, this can lead to errors and difficult checking. moabb/moabb/pipelines/utils.py Line 216 in d2edb29
moabb/moabb/pipelines/utils.py Line 267 in d2edb29
Besides improving documentation, the question now is, what should we do here? |
I think it’s fine to keep both methods, as different users might have different habits. Because of the edge effects, they will not give the same results, so we don’t have much to test here. |
the core question is: does this affect performances of the different pipelines? |
This could be a good onboarding project for a Bachelor/Master student :) |
If you have time after the ICLR review period, it would be great if you could take a look.
The text was updated successfully, but these errors were encountered: