You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It may be good to bring to your attention that I am changing the default argument minloadcrit value in GGIR from 72 to 168. See description and motivation in wadpac/GGIR#1101
This will slow down the auto-calibration procedure but seems worth it when user wants to rely on ENMO metric. On the other hand, the results I present in that issue indicate also that for other metrics we may be fine with less than 72 hours of data or skipping the auto-calibration entirely as we already hinted at in the 2014 publication. So, it may be worth exploring whether a more clever setting of minloadcrit depending on acceleration metrics to be derived could optimise processing time without compromising the output.
The text was updated successfully, but these errors were encountered:
It may be good to bring to your attention that I am changing the default argument
minloadcrit
value in GGIR from 72 to 168. See description and motivation in wadpac/GGIR#1101This will slow down the auto-calibration procedure but seems worth it when user wants to rely on ENMO metric. On the other hand, the results I present in that issue indicate also that for other metrics we may be fine with less than 72 hours of data or skipping the auto-calibration entirely as we already hinted at in the 2014 publication. So, it may be worth exploring whether a more clever setting of minloadcrit depending on acceleration metrics to be derived could optimise processing time without compromising the output.
The text was updated successfully, but these errors were encountered: