Skip to content
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

Spindle peak distance hardcoded #4

Open
jens-k opened this issue Sep 9, 2020 · 3 comments
Open

Spindle peak distance hardcoded #4

jens-k opened this issue Sep 9, 2020 · 3 comments
Assignees

Comments

@jens-k
Copy link
Member

jens-k commented Sep 9, 2020

@NNiethard
Can we make these 100/125 ms dependent on sampling rate and detection frequency?

if sum(double(isLongEnough))>1 && sum(double(MaxIsThere))>1 && max(diff(locs))<100 %check if long enough spindle is present and check that no peak to peak distance is more than 125ms

@jens-k
Copy link
Member Author

jens-k commented Sep 14, 2020

Now its 0.125 * Fs. Can we replace the first factor by 1/cfg.spi_freq(1) ?

@NNiethard
Copy link
Contributor

In general yes however this might lead to bad results if someone desided to use a very narrow filter band. Maybe we can include a warning?

@jens-k
Copy link
Member Author

jens-k commented Oct 15, 2020

After skype: Let's have this as a cfg option. e.g.:

cfg.spi_maxpeakdist = 0.125; % 0 for 'off'

@jens-k jens-k self-assigned this Nov 3, 2020
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

No branches or pull requests

2 participants