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

Handling of sleep stages (animals vs. humans) #6

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

Handling of sleep stages (animals vs. humans) #6

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

Comments

@jens-k
Copy link
Member

jens-k commented Sep 10, 2020

Should we allow the user to provide names for the NREM sleep stages in output.info.cfg.code_NREM (this would be another cfg entry given to detectEvents, since we don't have a cfg here..)?

This would be a way to disambiguate stages names in animal vs. human recordings.

Currently, if one scores all NREM as '2', this will be shown as 'S2'. Is that a problem? We could show it as '2' to make clear, this is taken from the hypnogram and doesn't have to adhere to Rechtschaffen & Kales.

@jens-k
Copy link
Member Author

jens-k commented Sep 11, 2020

Part of this issue is:
Should plotDetectedEvents plot all sleep stages present in the data or only the stages over which detection was done? In the perfect case, I would want to tell the function: NREM is [2 3 4] but please detect spindles only in 2. On the other hand, the functions should not get too complex (=harder to use for the user and to maintain for us).

We could assume the user always provides all NREM sleep stages but then note down for each spindle the respective sleep stage. For that, one would have to save them instead as a 2xn vector as a 3xn vector (or better: an nx3 vector).

@jens-k
Copy link
Member Author

jens-k commented Sep 14, 2020

@NNiethard ?

@NNiethard
Copy link
Contributor

Yes, this definetly would make sense.

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