Sleep diary format validation issue - "only appears to have time indicators for SPT" error despite correct TimeInBed format #1355
-
Issue DescriptionI'm encountering an error in GGIR Part 4 when processing sleep diary data that appears to be correctly formatted for Time in Bed analysis. The error suggests my data has SPT indicators when it actually has TimeInBed format. Error MessageError: The sleep diary as provided only appears to have time indicators for SPT and not for the Time in Bed, while parameter sleepwindowType is set to TimeInBed. Either change sleepwindowType to "SPT" or change your sleep diary column names for sleep timing to "outbed" and "inbed". Sleep Diary Format and GGIR ConfigurationMy CSV file has the following structure: Attempted Solutions Verified column names contain "inbed" and "outbed" as expected Questions Column naming: Could the _N1, _N2 suffixes be causing detection issues? Should I use inbed1, outbed1 instead? |
Beta Was this translation helpful? Give feedback.
Replies: 4 comments
-
|
I have the same issue. It worked with previous data and with the same taxology, now I get this Error when I run with "TimeInBed". |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for reporting. Your sleeplog format is fine. You are using the basic format for the sleeplog where column names are ignored by GGIR. The basic format for the sleeplog can be tested with GGIR function which indicates that the problem is that GGIR currently automatically assumes that any basic sleeplog format must be SPT and not TimeInBed. I suspect this issue emerged after I expanded the functionality for advanced format sleeplog diary in the past year. I am now preparing a fix. |
Beta Was this translation helpful? Give feedback.
-
|
Thank You! |
Beta Was this translation helpful? Give feedback.
-
|
The fix is now part of the 3.2-10 release I made yesterday. It is only available on GitHub for now. I aim to make a new CRAN release in September. You can install the GitHub release of GGIR with: |
Beta Was this translation helpful? Give feedback.
The fix is now part of the 3.2-10 release I made yesterday. It is only available on GitHub for now. I aim to make a new CRAN release in September.
You can install the GitHub release of GGIR with: