GGIR training materials

The assignment for each session are detailed in the slides (see above).

You can use the data as provided in the link below. These data files are all collected on the wrist. Make sure you unzip the folder after downloading.

If you have your own raw accelerometer data files with matching sleeplog you could use those too. However, please be aware that we may not have time during the training to troubleshoot all problems specific to your own data.

During the GGIR training you can ask us questions in the Zoom chat or via email. Outside the training we prefer that you ask your questions in a public place. A public discussion enables others to learn from our answers, it reduces the chance that we have to answer the same question twice, it increases the chance that someone else can answer your question when we are not available, and it gives recognition for the voluntary time we put into helping GGIR users outside the training.

Where to ask questions/report problems?

• The GGIR google group. Please note that this also works as an email list: Messages sent will be delivered to list members Inbox and deleting a message from the online platform does not delete it from their inbox. So, if you post something and regret it then please send a follow-up message to indicate that you no longer need help.
• If you are familiar with GitHub then consider GGIR GitHub issue tracker.

Keep in mind that the people answering it are doing this voluntary, so it is important that you attempt to write an effective message.

What constitutes a good help request?

• A short, clear and concise description of your problem.
• Include steps to reproduce the behavior, where you need to assess what information might be relevant:
  • sensor brand
  • data format, e.g. .bin, .csv.
  • approximate recording duration.
• Copy of R command used or config.csv file
• Explain what you have done to investigate the issue yourself. For example, did you try processing your data based on GGIR’s default argument values first?
• A clear and concise description of what you expected to happen.
• Screenshots: If applicable, add screenshots to help explain your problem. Note that usually we are not only interested in seeing the error message in red, but all GGIR output to the console.
• Example files: It often is a lot easier for us to investigate an issue if you could share an example file that allows for reproducing the problem. This does not always have to be the raw acceleration file but could also be the “.RData” file stored in output subfolder meta/basic. You will learn more about this in the GGIR training.