search

ctmm-initiative / ctmm

Continuous-Time Movement Modeling. Functions for identifying, fitting, and applying continuous-space, continuous-time stochastic movement models to animal tracking data.
http://biology.umd.edu/movement.html
47 stars 12 forks source link

checking ctmm takes over 3 hours #54

Closed tdhock closed 7 months ago

tdhock commented 7 months ago

Hi @chfleming I am trying to check ctmm, to determine if there are any revdep issues with data.table https://github.com/tdhock/data.table-revdeps/issues/17#issuecomment-1951449062

I have observed that checking ctmm takes over 3 hours, with most of the time being spent in the "re-building of vignette outputs" step. In your experience, is it normal for checking ctmm to take so long? If not, is there any special setup that you would recommend to speed up checks? Would you please consider removing, or modifying the code, in some of the vignettes, in order to make re-building faster? (at least in the version you submit to CRAN)

For context, we are checking every revdep of data.table every day, and there are 1400+ such packages. Median check time is about 10 minutes over all of those packages. ctmm is in the top 2 slowest. It runs out of time after a limit of 9 hours. 99% of packages take 2 hours or less total check time.

Thanks in advance for any help or clarification you can provide.

chfleming commented 7 months ago

Hi @tdhock,

A couple of hours is normal. Both the vignettes and the examples contain many real-data examples, which end-users greatly appreciate. The CRAN package should contain pre-compiled vignettes and examples that take a while to run should be wrapped in \donttest{}. If you do not re-compile the vignettes nor test the \donttest{} examples, then it shouldn't take very long.

tdhock commented 7 months ago

Hi Christen, thanks for the quick feedback! I notice on https://cloud.r-project.org/web/checks/check_results_ctmm.html that there is --no-vignettes under Flags, so maybe we can try that to save time.