CRAN Package Check Results for Package dyngen

Last updated on 2026-02-08 17:49:46 CET.

Flavor Version Tinstall Tcheck Ttotal Status Flags
r-devel-linux-x86_64-debian-clang 1.0.5 23.33 207.96 231.29 ERROR
r-devel-linux-x86_64-debian-gcc 1.0.5 15.44 139.99 155.43 ERROR
r-devel-linux-x86_64-fedora-clang 1.0.5 39.00 332.55 371.55 ERROR
r-devel-linux-x86_64-fedora-gcc 1.0.5 39.00 357.74 396.74 ERROR
r-devel-windows-x86_64 1.0.5 24.00 207.00 231.00 ERROR
r-patched-linux-x86_64 1.0.5 23.28 196.00 219.28 ERROR
r-release-linux-x86_64 1.0.5 21.31 203.45 224.76 ERROR
r-release-macos-arm64 1.0.5 NOTE
r-release-macos-x86_64 1.0.5 13.00 180.00 193.00 NOTE
r-release-windows-x86_64 1.0.5 22.00 206.00 228.00 NOTE
r-oldrel-macos-arm64 1.0.5 NOTE
r-oldrel-macos-x86_64 1.0.5 13.00 139.00 152.00 NOTE
r-oldrel-windows-x86_64 1.0.5 35.00 270.00 305.00 ERROR

Additional issues

donttest

Check Details

Version: 1.0.5
Check: CRAN incoming feasibility
Result: NOTE Maintainer: ‘Robrecht Cannoodt <rcannood@gmail.com>’ Package CITATION file contains call(s) to old-style citEntry(). Please use bibentry() instead. Flavors: r-devel-linux-x86_64-debian-clang, r-devel-linux-x86_64-debian-gcc

Version: 1.0.5
Check: Rd files
Result: NOTE checkRd: (-1) generate_kinetics.Rd:57: Lost braces; missing escapes or markup? 57 | By default, sampled from {-1, 1} with probabilities {.25, .75}. | ^ checkRd: (-1) generate_kinetics.Rd:57: Lost braces; missing escapes or markup? 57 | By default, sampled from {-1, 1} with probabilities {.25, .75}. | ^ Flavors: r-devel-linux-x86_64-debian-clang, r-devel-linux-x86_64-debian-gcc, r-devel-linux-x86_64-fedora-clang, r-devel-linux-x86_64-fedora-gcc, r-devel-windows-x86_64, r-patched-linux-x86_64, r-release-linux-x86_64, r-release-macos-arm64, r-release-macos-x86_64, r-release-windows-x86_64, r-oldrel-macos-arm64, r-oldrel-macos-x86_64, r-oldrel-windows-x86_64

Version: 1.0.5
Check: examples
Result: ERROR Running examples in ‘dyngen-Ex.R’ failed The error most likely occurred in: > base::assign(".ptime", proc.time(), pos = "CheckExEnv") > ### Name: get_timings > ### Title: Return the timings of each of the dyngen steps > ### Aliases: get_timings > > ### ** Examples > > data("example_model") > timings <- get_timings(example_model) Error in `summarise()`: ℹ In argument: `task = .data$task[-length(.data$task)]`. ℹ In group 2: `group = "2_tf_network"`. Caused by error: ! `task` must be size 1, not 2. ℹ To return more or less than 1 row per group, use `reframe()`. Backtrace: ▆ 1. ├─dyngen::get_timings(example_model) 2. │ └─model$timings %>% group_by(.data$group) %>% ... 3. ├─dplyr::summarise(...) 4. ├─dplyr:::summarise.grouped_df(...) 5. │ └─dplyr:::summarise_cols(.data, dplyr_quosures(...), by, "summarise") 6. │ └─base::withCallingHandlers(...) 7. ├─dplyr:::dplyr_internal_error(...) 8. │ └─rlang::abort(class = c(class, "dplyr:::internal_error"), dplyr_error_data = data) 9. │ └─rlang:::signal_abort(cnd, .file) 10. │ └─base::signalCondition(cnd) 11. └─dplyr (local) `<fn>`(`<dpl:::__>`) 12. └─dplyr (local) handler(cnd) 13. └─rlang::abort(message, class = error_class, parent = parent, call = error_call) Execution halted Examples with CPU (user + system) or elapsed time > 5s user system elapsed backbone_models 2.546 0.26 12.896 Flavor: r-devel-linux-x86_64-debian-clang

Version: 1.0.5
Check: examples
Result: ERROR Running examples in ‘dyngen-Ex.R’ failed The error most likely occurred in: > base::assign(".ptime", proc.time(), pos = "CheckExEnv") > ### Name: get_timings > ### Title: Return the timings of each of the dyngen steps > ### Aliases: get_timings > > ### ** Examples > > data("example_model") > timings <- get_timings(example_model) Error in `summarise()`: ℹ In argument: `task = .data$task[-length(.data$task)]`. ℹ In group 2: `group = "2_tf_network"`. Caused by error: ! `task` must be size 1, not 2. ℹ To return more or less than 1 row per group, use `reframe()`. Backtrace: ▆ 1. ├─dyngen::get_timings(example_model) 2. │ └─model$timings %>% group_by(.data$group) %>% ... 3. ├─dplyr::summarise(...) 4. ├─dplyr:::summarise.grouped_df(...) 5. │ └─dplyr:::summarise_cols(.data, dplyr_quosures(...), by, "summarise") 6. │ └─base::withCallingHandlers(...) 7. ├─dplyr:::dplyr_internal_error(...) 8. │ └─rlang::abort(class = c(class, "dplyr:::internal_error"), dplyr_error_data = data) 9. │ └─rlang:::signal_abort(cnd, .file) 10. │ └─base::signalCondition(cnd) 11. └─dplyr (local) `<fn>`(`<dpl:::__>`) 12. └─dplyr (local) handler(cnd) 13. └─rlang::abort(message, class = error_class, parent = parent, call = error_call) Execution halted Flavors: r-devel-linux-x86_64-debian-gcc, r-patched-linux-x86_64, r-release-linux-x86_64

Version: 1.0.5
Check: examples
Result: ERROR Running examples in ‘dyngen-Ex.R’ failed The error most likely occurred in: > ### Name: get_timings > ### Title: Return the timings of each of the dyngen steps > ### Aliases: get_timings > > ### ** Examples > > data("example_model") > timings <- get_timings(example_model) Error in `summarise()`: ℹ In argument: `task = .data$task[-length(.data$task)]`. ℹ In group 2: `group = "2_tf_network"`. Caused by error: ! `task` must be size 1, not 2. ℹ To return more or less than 1 row per group, use `reframe()`. Backtrace: ▆ 1. ├─dyngen::get_timings(example_model) 2. │ └─model$timings %>% group_by(.data$group) %>% ... 3. ├─dplyr::summarise(...) 4. ├─dplyr:::summarise.grouped_df(...) 5. │ └─dplyr:::summarise_cols(.data, dplyr_quosures(...), by, "summarise") 6. │ └─base::withCallingHandlers(...) 7. ├─dplyr:::dplyr_internal_error(...) 8. │ └─rlang::abort(class = c(class, "dplyr:::internal_error"), dplyr_error_data = data) 9. │ └─rlang:::signal_abort(cnd, .file) 10. │ └─base::signalCondition(cnd) 11. └─dplyr (local) `<fn>`(`<dpl:::__>`) 12. └─dplyr (local) handler(cnd) 13. └─rlang::abort(message, class = error_class, parent = parent, call = error_call) Execution halted Flavors: r-devel-linux-x86_64-fedora-clang, r-devel-linux-x86_64-fedora-gcc, r-devel-windows-x86_64, r-oldrel-windows-x86_64

These binaries (installable software) and packages are in development.
They may not be fully stable and should be used with caution. We make no claims about them.
Health stats visible at Monitor.