dur_day_spt_min not equal to 1440 min (in midnight-midnight reports)

51 views
Skip to first unread message

Emilia Eliasson

unread,
Apr 9, 2025, 7:26:33 AMApr 9
to R package GGIR

Hello,

I am new to GGIR and have encountered an issue that seems to be similar to what others have reported recently in this group. I’m hoping someone can provide some clarity on the matter.

We are using GGIR package version 3.2 to analyze accelerometer data from Actigraph GT3X-BT devices. Study participants have been instructed to wear the accelerometer on their non-dominant wrist for 3 weeks, 24/7, only taking it off during water-based activities.

In both the cleaned daysummary (part5_daysummary_MM_L44.8M100.6V428.8_T5A5) and full daysummay report (part5_daysummary_full_MM_L44.8M100.6V428.8_T5A5), we have observed unexpected values for the dur_day_spt_min variable. Since we are working with midnight-to-midnight reports, we would expect all values for dur_day_spt_min to be 1440 minutes (24 hours). Although most of the full windows in our output files are 1440 minutes, some deviate in both the cleaned and full daysummary.

Specifically, 14 of the days present in part5_daysummary_MM_L44.8M100.6V428.8_T5A5 are longer than 1440 minutes (ranging from 1500 to 3720 minutes). Additionally, three days show durations shorter than expected (each is 1380 minutes). The report contains nearly 900 days, so this issue does not occur for every participant. Furthermore, it tends to affect the first or last window of the measurement period.

I have attached the script we have been using for reference.

We are unsure how to interpret these results or whether something went wrong during the analysis. Any advice on this issue would be greatly appreciated.

Thank you in advance!

Emilia

GGIR_script_0408.R

Vincent van Hees

unread,
Apr 21, 2025, 12:00:17 PMApr 21
to Emilia Eliasson, R package GGIR
Hello Emilia,

When you refer to other posts please include a link to those posts to make it easier for readers to oversee what you are referring to.

Please provide example data (RData file from meta/basic folder) to facilitate reproducing and investigating your issue. An R script alone is not enough to reproduce an issue.

With kind regards,

Vincent

Dr. Vincent van Hees | Independent consultant | https://accelting.com/
image

--
You received this message because you are subscribed to the Google Groups "R package GGIR" group.
To unsubscribe from this group and stop receiving emails from it, send an email to RpackageGGIR...@googlegroups.com.
To view this discussion, visit https://groups.google.com/d/msgid/RpackageGGIR/35b989ff-a944-40bb-b860-79872592785en%40googlegroups.com.

Emilia Eliasson

unread,
Apr 22, 2025, 9:39:56 AMApr 22
to R package GGIR

Hi Vincent,

Thank you for your reply.

The previous posts I was referring to are:

I noticed your response to the first post, where you mentioned that the values of the dur_day_spt_min_pla variable can exceed 1440 minutes if they are derived from the WW-report. However, I find it interesting that I observe similarly high durations even when analyzing the MM-reports.

Unfortunately, I am unable to share example data due to data protection regulations, so I understand that it might be difficult to investigate the issue I am encountering. That said, since I have observed this behavior across all batches of my data, I wanted to check whether there might be an obvious oversight in my analysis or potentially a bug in GGIR contributing to this.

Kind regards,
Emilia

Vincent van Hees

unread,
May 1, 2025, 10:30:12 AMMay 1
to Emilia Eliasson, R package GGIR
HI Emilia,

This should now be fixed in GGIR release 3.2-6.
See also my response to https://groups.google.com/g/RpackageGGIR/c/0nvXVHcCVUU/m/hA0270hQDQAJ, but you can ignore the installation instruction I provided there because it is now part of the new GGIR release.

Thanks,

Vincent
Reply all
Reply to author
Forward
0 new messages