* using log directory ‘/srv/hornik/tmp/CRAN_pretest/OptOTrials.Rcheck’ * using R Under development (unstable) (2025-08-22 r88678) * 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 forky/sid * using session charset: UTF-8 * checking for file ‘OptOTrials/DESCRIPTION’ ... OK * checking extension type ... Package * this is package ‘OptOTrials’ version ‘1.0’ * package encoding: UTF-8 * checking CRAN incoming feasibility ... [3s/3s] NOTE Maintainer: ‘Yeonhee Park ’ New submission Possibly misspelled words in DESCRIPTION: OptOTrials (3:8) RCTs (9:92) No Authors@R field in DESCRIPTION. Please add one, modifying Authors@R: c(person(given = "Yeonhee", family = "Park", role = c("aut", "cre"), email = "yeonheepark@skku.edu"), person(given = "Yudi", family = "Wang", role = "aut"), person(given = "Zhanpeng", family = "Xu", role = "aut")) as necessary. The Title field starts with the package name. The Title field should be in title case. Current version is: ‘OptOTrials: An R package for Designing and Simulating Optimal Two-Stage Clinical Trials for Ordered Categorical Data’ In title case that is: ‘OptOTrials: An R Package for Designing and Simulating Optimal Two-Stage Clinical Trials for Ordered Categorical Data’ Found the following \keyword or \concept entries which likely give several index terms: File ‘OptOTrials-package.Rd’: \keyword{Adaptive design, Mann-Whitney-Wilcoxon te [TRUNCATED] * 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 ‘OptOTrials’ can be installed ... [1s/1s] OK * checking package directory ... OK * checking for future file timestamps ... 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 ... [0s/0s] OK * checking whether the package can be loaded with stated dependencies ... [0s/0s] OK * checking whether the package can be unloaded cleanly ... [0s/0s] OK * checking whether the namespace can be loaded with stated dependencies ... [0s/0s] OK * checking whether the namespace can be unloaded cleanly ... [0s/0s] OK * checking loading without being on the library search path ... [0s/0s] 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 ... [3s/3s] OK * checking Rd files ... [0s/0s] OK * checking Rd metadata ... OK * checking Rd line widths ... NOTE Rd file 'op.F.Rd': \examples lines wider than 100 characters: op.F(alpha, beta, p1, p2, method="W", n1=out[1], t1=out[2], n2=out[3], t2=out[4], nsim = 10000, lambda = 1) op.F(alpha, beta, p1, p1, method="W", n1=out[1], t1=out[2], n2=out[3], t2=out[4], nsim = 10000, lambda = 1) Rd file 'op.FS.Rd': \examples lines wider than 100 characters: op.FS(alpha, beta, p1, p2, method="W", n1=out[1], t1l=out[2], t1u=out[3], n2=out[4], t2=out[5], nsim = 10000, lambda = 1) op.FS(alpha, beta, p1, p1, method="W", n1=out[1], t1l=out[2], t1u=out[3], n2=out[4], t2=out[5], nsim = 10000, lambda = 1) These lines will be truncated in the PDF manual. * 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 examples ... [177s/177s] NOTE Examples with CPU (user + system) or elapsed time > 5s user system elapsed op.FS 86.198 1.851 88.100 op.F 62.041 0.608 62.688 op.1stage 24.809 0.327 25.153 * checking PDF version of manual ... [3s/3s] OK * checking HTML version of manual ... [1s/1s] OK * checking for non-standard things in the check directory ... OK * checking for detritus in the temp directory ... OK * DONE Status: 3 NOTEs