Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Slow down of as.POSIXct() when converting numeric data with origin argument specified #1263

Open
vincentvanhees opened this issue Jan 29, 2025 · 0 comments · May be fixed by #1264
Open

Slow down of as.POSIXct() when converting numeric data with origin argument specified #1263

vincentvanhees opened this issue Jan 29, 2025 · 0 comments · May be fixed by #1264

Comments

@vincentvanhees
Copy link
Member

@forget999 could you please share with us what solved the problem for you?

Doing so will help:

  • Future GGIR users with the same problem reading this thread.
  • Us to understand what aspect of GGIR functionality or documentation is not clear enough yet.

Thanks for your reply! I have reset the "part6_threshold_combi" parameters number to meet the physical activity requirements of my research.
In addition, I think there is one thing that needs to be improved. The new version v3.1-11 of GGIR takes too long time to run part6, which takes an hour. But in the version v3.1-5, it is quite fast. I don't know where the difference is, or what adjustments can speed up the running speed of part6. If you have any suggestions, please let me know. Thank you!

Originally posted by @forget999 in #1262

This seems caused by my effort to make GGIR backward compatible with R 4.2.0 by adding the origin argument. Backward comparability at the price of a huge slow down is undesirable, so this needs fixing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
1 participant