xiangnandang/ggir_workshop

public repo for ggir workshop

ggir_workshop's Issues

Question for Vincent

Vincent, please see the list of questions from us as follows. Thanks a lot for your help!

1. If we want to implement another imputation procedure while running GGIR, how can we do that?
2. What is the difference between UK Biobank and GGIR from your perspective?
3. In Van Hees et al 2018, the z-angle is a feature used to detect sleep period time (SPT) window, and the raw signal data from each of the axes were used without prior gravity removal. Would that affect the results or it does not matter for detecting the sustained inactivity bouts using the signal data with or without prior gravity removal?
4. Are the features roll, pitch, and yaw (Ellis 2016) calculated from the three signal axes before applying a low-pass filter to separate the gravity out? But the roll, pitch and yaw angles of the gravity direction were calculated after extracting the gravity from the raw signal on each axis? If so, why not calculating the roll, pitch and yaw directly from the axes after the gravity have been removed?
5. In part 2 of GGIR, the unreliable signal sections were identified and replaced by imputed values, are the "unreliable signal sections" including only the non-wear sections and clipping sections detected by the algorithm? If not, what else do they include?

example of selectdaysfile=c() used in part 1

Vincent, could you please provide a selectdaysfile as an example?

config.csv

Hi Vincent, config.csv is a great addition to encourage reproducible ggir runs. We know locally defined same name parameters have higher priority than config.csv and config.csv is not meant for human consumption, but would you still explain the structure of config.csv and maybe demo a use?