* using log directory ‘/home/hornik/tmp/R.check/r-devel-clang/Work/PKGS/BCT.Rcheck’
* using R Under development (unstable) (2025-07-13 r88407)
* 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 ‘BCT/DESCRIPTION’ ... OK
* checking extension type ... Package
* this is package ‘BCT’ version ‘1.2’
* package encoding: UTF-8
* checking CRAN incoming feasibility ... [1s/1s] NOTE
Maintainer: ‘Valentinian Mihai Lungu <valentinian.mihai@gmail.com>’

No Authors@R field in DESCRIPTION.
Please add one, modifying
  Authors@R: c(person(given = "Ioannis",
                      family = "Papageorgiou",
                      role = "aut"),
               person(given = c("Valentinian", "Mihai"),
                      family = "Lungu",
                      role = c("aut", "cre"),
                      email = "valentinian.mihai@gmail.com"),
               person(given = "Ioannis",
                      family = "Kontoyiannis",
                      role = "aut"))
as necessary.

The Description field contains
  April 2022. Available at: <arXiv:2007.14900> [stat.ME], July 2020] and
  using Bayesian Context Trees' <arXiv:2203.04341> [stat.ME], March
Please refer to arXiv e-prints via their arXiv DOI <doi:10.48550/arXiv.YYMM.NNNNN>.
* 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 whether package ‘BCT’ can be installed ... OK
See 'https://www.r-project.org/nosvn/R.check/r-devel-linux-x86_64-debian-clang/BCT-00install.html' for details.
* used C++ compiler: ‘Debian clang version 19.1.7 (3+b1)’
* checking C++ specification ... NOTE
  Specified C++11: please drop specification unless essential
* 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/1s] OK
* checking whether the package can be loaded with stated dependencies ... [0s/0s] OK
* checking whether the package can be unloaded cleanly ... [0s/1s] OK
* checking whether the namespace can be loaded with stated dependencies ... [0s/1s] OK
* checking whether the namespace can be unloaded cleanly ... [0s/1s] OK
* checking loading without being on the library search path ... [0s/1s] 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 ... [6s/8s] OK
* checking Rd files ... [0s/1s] NOTE
checkRd: (-1) gene_s.Rd:17: Lost braces; missing escapes or markup?
    17 | giving the virus access to the cell and thus facilitating the COVID-19 disease. The gene sequence is mapped to the alphabet {0,1,2,3} via the obvious map A->0, C->1, G->2, T->3.
       |                                                                                                                             ^
checkRd: (-1) sars_cov_2.Rd:16: Lost braces; missing escapes or markup?
    16 | It consists of n = 29903 base pairs. The gene sequence is mapped to the alphabet {0,1,2,3} via the obvious map A->0, C->1, G->2, T->3.
       |                                                                                  ^
* 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 LazyData ... OK
* checking data for ASCII and uncompressed saves ... OK
* checking line endings in C/C++/Fortran sources/headers ... OK
* checking pragmas in C/C++ headers and code ... OK
* checking compilation flags used ... OK
* checking compiled code ... OK
* checking examples ... [4s/5s] OK
* checking PDF version of manual ... [5s/6s] OK
* checking HTML version of manual ... [1s/2s] OK
* checking for non-standard things in the check directory ... OK
* DONE
Status: 3 NOTEs