NSRR staff
Boston, MA
0000-0002-0506-8368
Top Topics
Recent Topics
Thanks for using the site and for your willingness to share your tool. Maybe you could host the code on GitHub/GitLab or a similar service? Feel free to post the link here when that's complete!
Some of the NSRR tools in ongoing development have public repositories here: https://gitlab-scm.partners.org/zzz-public
Yes, I think running with the "--fast" flag should work. You can't tell the gem to start at a specific file; it still needs to run through all the prior files and compare filesizes.
Hi - I'll ask another member of the team to comment on your first two questions.
Regarding #3 - SHHS had a 12-lead ECG reading done in clinic (i.e. not part of the overnight PSG). Some result variables from the 12-lead ECG are here: https://sleepdata.org/datasets/shhs/variables?folder=Clinical+Data%2FDiagnostic+Studies%2FElectrocardiogram
It sounds like for your research you will focus on the ECG signals in the overnight PSG recordings.
Good questions - this sort of "reliability" was assessed for the beginning and end of every REST interval in the actigraphy scoring. The actigraphy scorer made a quick judgement about whether indicators (e.g., event marker from device button press, diary, light levels, activity levels) were reliable with one another and recorded these on the QS form.
whether the "interval" info reported in the actigraphy file is considered reliable or not
All of the REST intervals in the actigraphy files were deemed to be valid and usable by the scorer. If, for instance, a day of actigraphy had lots of non-wear time (particularly during a nighttime sleep window) then the day would be entirely excluded and you would not find an interval in the actigraphy file.
The "reliability" here is an assessment of how well the different indicators align (or don't). It is not a judgment on whether or not the interval itself is usable (or not).
if I can access the reported reliability on a detected rest episode basis
No, these reliability indicators (from QS form) were not included in the shared data package.
I ran the command "nsrr download shhs/polysomnography/edfs --fresh" and it worked.
Please post a screenshot if you don't get the same result.
Thanks for using the site. What happens if you run the nsrr download shhs command? Try it without entering the gem console.
The STAGES team did not provide such documentation. We (the NSRR) intend to start depositing harmonized EDFs and annotations for many datasets this year, which would help users overcome challenges such as this.
Thanks for using the site!
Thanks for checking out the site. The STAGES team did not provide such details. You might try finding other documentation on the web about the Amazfit Arc, which was the device used in STAGES.
I think you're referring to the ABC dataset. Please reference this page for more information on the PSG signals: https://www.sleepdata.org/datasets/abc/pages/montage-and-sampling-rate-information.md
I'm guessing you're looking for F3, F4, C3, C4, etc.
Hope that helps!
Yes, you'll hear back about your data request in the next two weeks. You'll receive an email.
Can you try downloading the RubyInstaller for Windows here? https://rubyinstaller.org/
Then after installing Ruby and the DevKit, you should run "gem install nsrr" at the command prompt, which will hopefully install NSRR gem version 8.0.0.
No need to apologize - other users in the future may have similar issues, so thanks for bringing your questions to the forum.