• using R Under development (unstable) (2025-06-25 r88360)
• using platform: x86_64-pc-linux-gnu
• R was compiled by     Debian clang version 19.1.7 (3+b1)     Debian flang-new version 19.1.7 (3+b1)
• running under: Debian GNU/Linux 13 (trixie)
• using session charset: UTF-8
• checking for file ‘grizbayr/DESCRIPTION’ ... OK
• checking extension type ... Package
• this is package ‘grizbayr’ version ‘1.3.5’
• package encoding: UTF-8
• checking CRAN incoming feasibility ... [1s/1s] NOTE Maintainer: ‘Ryan Angi <angi.ryan@gmail.com>’ No Authors@R field in DESCRIPTION. Please add one, modifying   Authors@R: person(given = "Ryan",                     family = "Angi",                     role = c("aut", "cre"),                     email = "angi.ryan@gmail.com") as necessary.
• checking package namespace information ... OK
• checking package dependencies ... OK
• checking if this is a source package ... OK
• checking if there is a namespace ... OK
• checking for executable files ... OK
• checking for hidden files and directories ... OK
• checking for portable file names ... OK
• checking for sufficient/correct file permissions ... OK
• checking serialization versions ... OK
• checking whether package ‘grizbayr’ can be installed ... OK See the install log for details.
• checking package directory ... OK
• checking for future file timestamps ... OK
• checking ‘build’ directory ... OK
• checking DESCRIPTION meta-information ... OK
• checking top-level files ... OK
• checking for left-over files ... OK
• checking index information ... OK
• checking package subdirectories ... OK
• checking code files for non-ASCII characters ... OK
• checking R files for syntax errors ... OK
• checking whether the package can be loaded ... [1s/2s] OK
• checking whether the package can be loaded with stated dependencies ... [1s/1s] OK
• checking whether the package can be unloaded cleanly ... [1s/1s] OK
• checking whether the namespace can be loaded with stated dependencies ... [1s/1s] OK
• checking whether the namespace can be unloaded cleanly ... [1s/2s] OK
• checking loading without being on the library search path ... [1s/2s] OK
• checking use of S3 registration ... OK
• checking dependencies in R code ... OK
• checking S3 generic/method consistency ... OK
• checking replacement functions ... OK
• checking foreign function calls ... OK
• checking R code for possible problems ... [8s/10s] OK
• checking Rd files ... [1s/1s] NOTE checkRd: (-1) sample_cm_per_click.Rd:13: Lost braces; missing escapes or markup?     13 | \item{priors}{Optional list of priors {alpha0, beta0} for Beta, {k0, theta0} for Gamma Inverse Revenue,        | ^ checkRd: (-1) sample_cm_per_click.Rd:13: Lost braces; missing escapes or markup?     13 | \item{priors}{Optional list of priors {alpha0, beta0} for Beta, {k0, theta0} for Gamma Inverse Revenue,        | ^ checkRd: (-1) sample_cm_per_click.Rd:14: Lost braces; missing escapes or markup?     14 | and {k01, theta01} for Gamma Cost (uses alternate priors so they can be different from Revenue).        | ^ checkRd: (-1) sample_cpa.Rd:13: Lost braces; missing escapes or markup?     13 | \item{priors}{Optional list of priors {alpha0, beta0} for Beta and {k0, theta0}        | ^ checkRd: (-1) sample_cpa.Rd:13: Lost braces; missing escapes or markup?     13 | \item{priors}{Optional list of priors {alpha0, beta0} for Beta and {k0, theta0}        | ^ checkRd: (-1) sample_cpc.Rd:12: Lost braces; missing escapes or markup?     12 | \item{priors}{Optional list of priors {k0, theta0} for Gamma.        | ^ checkRd: (-1) sample_rev_per_session.Rd:13: Lost braces; missing escapes or markup?     13 | \item{priors}{Optional list of priors {alpha0, beta0} for Beta        | ^ checkRd: (-1) sample_rev_per_session.Rd:14: Lost braces; missing escapes or markup?     14 | and {k0, theta0} for Gamma. Default \eqn{Beta(1,1)}        | ^ checkRd: (-1) sample_total_cm.Rd:13: Lost braces; missing escapes or markup?     13 | \item{priors}{Optional list of priors {alpha0, beta0} for Beta,        | ^ checkRd: (-1) sample_total_cm.Rd:14: Lost braces; missing escapes or markup?     14 | {k0, theta0} for Gamma Inverse Revenue, and {k01, theta01} for        | ^ checkRd: (-1) sample_total_cm.Rd:14: Lost braces; missing escapes or markup?     14 | {k0, theta0} for Gamma Inverse Revenue, and {k01, theta01} for        | ^
• checking Rd metadata ... OK
• checking Rd line widths ... OK
• checking Rd cross-references ... OK
• checking for missing documentation entries ... OK
• checking for code/documentation mismatches ... OK
• checking Rd \usage sections ... OK
• checking Rd contents ... OK
• checking for unstated dependencies in examples ... OK
• checking R/sysdata.rda ... OK
• checking installed files from ‘inst/doc’ ... OK
• checking files in ‘vignettes’ ... OK
• checking examples ... [26s/35s] OK Examples with CPU (user + system) or elapsed time > 5s                                user system elapsed estimate_value_remaining 8.985 0.101 11.462 estimate_win_prob_vs_baseline 7.549 0.047 10.637 estimate_win_prob 3.785 0.004 5.534
• checking for unstated dependencies in ‘tests’ ... OK
• checking tests ... [122s/145s] OK   Running ‘spelling.R’ [0s/0s]   Running ‘testthat.R’ [121s/144s]
• checking for unstated dependencies in vignettes ... OK
• checking package vignettes ... OK
• checking re-building of vignette outputs ... [271s/351s] OK
• checking PDF version of manual ... [5s/7s] OK
• checking HTML version of manual ... [2s/2s] OK
• checking for non-standard things in the check directory ... OK
• DONE

Status: 2 NOTEs