• using R Under development (unstable) (2023-09-21 r85196)
• using platform: x86_64-pc-linux-gnu
• R was compiled by
      gcc-13 (Debian 13.2.0-4) 13.2.0
      GNU Fortran (Debian 13.2.0-4) 13.2.0
• running under: Debian GNU/Linux trixie/sid
• using session charset: UTF-8
• checking for file ‘irt/DESCRIPTION’ ... OK
• checking extension type ... Package
• this is package ‘irt’ version ‘0.2.7’
• package encoding: UTF-8
• 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 ‘irt’ can be installed ... OK
  See the install log for details.
• used Fortran compiler: ‘GNU Fortran (Debian 13.2.0-4) 13.2.0’
• used C++ compiler: ‘g++-13 (Debian 13.2.0-4) 13.2.0’
• checking C++ specification ... NOTE
    Specified C++11: please drop specification unless essential
• 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 R files for non-ASCII characters ... OK
• checking R files for syntax errors ... OK
• checking whether the package can be loaded ... [1s/1s] 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/1s] OK
• checking loading without being on the library search path ... [1s/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 ... [35s/56s] OK
• checking Rd files ... [1s/3s] OK
• 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 ... NOTE
  Documented arguments not in \usage in documentation object 'print.cat_output':
    ‘object’
  
  Documented arguments not in \usage in documentation object '[[<-,Itempool,numeric,missing-method':
    ‘...’
  
  Documented arguments not in \usage in documentation object '[[<-,Response_set,numeric,missing-method':
    ‘...’
  
  Documented arguments not in \usage in documentation object '[[<-,Testlet,numeric,missing-method':
    ‘...’
  
  Functions with \usage entries need to have the appropriate \alias
  entries, and all their arguments documented.
  The \usage entries must correspond to syntactically valid R code.
  See chapter ‘Writing R documentation files’ in the ‘Writing R
  Extensions’ manual.
  S3 methods shown with full name in documentation object 'print.Item':
    ‘print.Item’
  
  The \usage entries for S3 methods should use the \method markup and not
  their full name.
  See chapter ‘Writing R documentation files’ in the ‘Writing R
  Extensions’ manual.
• checking Rd contents ... OK
• checking for unstated dependencies in examples ... OK
• checking line endings in C/C++/Fortran sources/headers ... OK
• checking line endings in Makefiles ... OK
• checking compilation flags in Makevars ... OK
• checking for GNU extensions in Makefiles ... OK
• checking for portable use of $(BLAS_LIBS) and $(LAPACK_LIBS) ... OK
• checking use of PKG_*FLAGS in Makefiles ... OK
• checking use of SHLIB_OPENMP_*FLAGS in Makefiles ... OK
• checking pragmas in C/C++ headers and code ... OK
• checking compilation flags used ... OK
• checking compiled code ... OK
• checking installed files from ‘inst/doc’ ... OK
• checking files in ‘vignettes’ ... OK
• checking examples ... [64s/108s] OK
  Examples with CPU (user + system) or elapsed time > 5s
                                  user system elapsed
  qip_index 5.727 0.012 10.455
  plot_empirical_icc2 5.434 0.006 9.432
  classification_indices 4.500 0.029 7.579
  plot.cat_output 3.928 0.035 5.735
  plot_info 3.542 0.007 5.435
  plot.Itempool 3.383 0.005 5.360
  classification_agreement_index 3.051 0.023 5.546
• checking for unstated dependencies in vignettes ... OK
• checking package vignettes in ‘inst/doc’ ... OK
• checking re-building of vignette outputs ... [19s/31s] OK
• checking PDF version of manual ... [11s/22s] OK
• checking HTML version of manual ... [7s/16s] OK
• checking for non-standard things in the check directory ... OK
• DONE

Status: 2 NOTEs