Skip to content

Conversation

zm711
Copy link
Contributor

@zm711 zm711 commented Feb 27, 2023

This is my first stab at incorporating a flag so that users can see whether or not their data has already had a notch filter applied. I couldn't think of a way to get it incorporated during the flow of the rest of the script, so I added the check right before the return to generate the flag.

@samuelgarcia

I added a `notch_filter_applied` info box as a boolean to indicate whether the Intan hardware applied the notch filter. 

For both rhs and rhd I just added the check at the bottom  before the return since we need to check both whether the `notch_filter_mode` > 0 and that the version is >= 3.0. I couldn't think of a way to fit it during the notch filter check without adding conditions into other functions which would slow everything down. It just means that the `notch_filter_applied` would be out of order compared to the other keys.
fixed rhd support. I didn't change support in doc string for rhs since I don't know what changes may have occurred in 2.x.
deleted extra spaces as suggested
@JuliaSprenger
Copy link
Member

Thanks for the changes, they look good to me. The failing tests unrelated (#1227) to the changes here.

@JuliaSprenger JuliaSprenger merged commit d806d0e into NeuralEnsemble:master Mar 1, 2023
@apdavison apdavison added this to the 0.13.0 milestone Jul 27, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants