* using log directory ‘/home/hornik/tmp/R.check/r-devel-gcc/Work/PKGS/ACSWR.Rcheck’ * using R Under development (unstable) (2025-07-14 r88410) * using platform: x86_64-pc-linux-gnu * R was compiled by gcc-14 (Debian 14.2.0-19) 14.2.0 GNU Fortran (Debian 14.2.0-19) 14.2.0 * running under: Debian GNU/Linux 13 (trixie) * using session charset: UTF-8 * checking for file ‘ACSWR/DESCRIPTION’ ... OK * checking extension type ... Package * this is package ‘ACSWR’ version ‘1.0’ * checking CRAN incoming feasibility ... [1s/1s] NOTE Maintainer: ‘Prabhanjan Tattar ’ No Authors@R field in DESCRIPTION. Please add one, modifying Authors@R: person(given = "Prabhanjan", family = "Tattar", role = c("aut", "cre"), email = "prabhanjannt@gmail.com") as necessary. Found the following \keyword or \concept entries which likely give several index terms: File ‘Disease.Rd’: \keyword{residual analysis, logistic regression} File ‘bs.Rd’: \keyword{score function, binomial distribution} File ‘chest.Rd’: \keyword{rootogram, militiamen} File ‘cloud.Rd’: \keyword{stem-and-leaf plot, cloud seeding experim [TRUNCATED] File ‘cork.Rd’: \keyword{multivariate dataset, singular value deco [TRUNCATED] File ‘cs.Rd’: \keyword{Cauchy random samples, score function} File ‘depression.Rd’: \keyword{Wilcoxon test, Hamilton depression scale} [TRUNCATED] File ‘flight.Rd’: \keyword{transformation, variance reduction} File ‘lowbwt.Rd’: \keyword{logistic regression, model selection} File ‘memory.Rd’: \keyword{fivenum, IQR} * 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 ‘ACSWR’ can be installed ... OK See 'https://www.r-project.org/nosvn/R.check/r-devel-linux-x86_64-debian-gcc/ACSWR-00install.html' for details. * 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 ... [4s/5s] OK * checking Rd files ... [1s/1s] NOTE checkRd: (-1) Ehrenfest.Rd:19: Lost braces 19 | In this experiment there are i balls in Urn I, and remaining 2n-i balls in Urn II. Then at any instance, the probability of selecting a ball from Urn I and placing it in Urn II is i/2n, and the other way of placing a ball from Urn II to Urn I is (2n-i)/2n. At each instant we let the number i of balls in the Urn I to be the state of the system. Thus, the state space is S = { 0, 1, 2, \ldots, 2n }. Then we can pass from state i only to either of the states i-1 or i+1. | ^ checkRd: (-1) Ehrenfest.Rd:20: Lost braces 20 | Here, S = {0, 1, \ldots, 2n}. | ^ * 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 contents of ‘data’ directory ... OK * checking data for non-ASCII characters ... [0s/0s] OK * checking data for ASCII and uncompressed saves ... OK * checking examples ... [2s/2s] OK * checking PDF version of manual ... [5s/7s] OK * checking HTML version of manual ... [2s/3s] OK * checking for non-standard things in the check directory ... OK * DONE Status: 2 NOTEs