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

Add option to let all sib count towards sleep when overlapping with TimeInBed #1223

Closed
5 of 6 tasks
vincentvanhees opened this issue Nov 6, 2024 · 1 comment · Fixed by #1239
Closed
5 of 6 tasks
Assignees

Comments

@vincentvanhees
Copy link
Member

vincentvanhees commented Nov 6, 2024

At the moment TimeInBed window type means that only sib are counted as sleep if they entirely overlap with TimeInBed motivated by the idea that sleep that overlaps with the edge of being in bed (self-reported) cannot be sleep.

In a project I am working on at the moment we see that actually it is more likely that the sleep diary is incorrect and that we should count those sibs as sleep.

To not break consistency with the past I will add a new option to change this.

This means that sleep latency can be negative.
Plan is to report negative latency at night level but ignore at person level. This does not affect any of the other sleep estimates only the latency estimate.

Next:

  • Add option to control when sibs are counted towards sleep
  • Deal with potential for negative latency, see above.
  • Add extra statistics to monitor how many nights had negative latency and were excluded from the person level latency estimate
  • Test in real dataset
  • Add control over whether this only applies for beginning or end of the night
  • Add extra statistics on sib during the hour before and after SPT as an indicator for whether sleep may have been missed. => better to do this in part 5 if we do it, but for now just visual inspection is best as way of method evaluation
@vincentvanhees
Copy link
Member Author

Status: This is now part of isseu967_selfreport to be test in that project, and I will merge all the work as one PR in the new year.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant