• using R version 4.4.2 (2024-10-31)
• using platform: x86_64-pc-linux-gnu
• R was compiled by     gcc-14 (Debian 14.2.0-8) 14.2.0     GNU Fortran (Debian 14.2.0-8) 14.2.0
• running under: Debian GNU/Linux trixie/sid
• using session charset: UTF-8
• checking for file ‘fclust/DESCRIPTION’ ... OK
• checking extension type ... Package
• this is package ‘fclust’ version ‘2.1.1.1’
• 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 ‘fclust’ can be installed ... OK See the install log for details.
• used C compiler: ‘gcc-14 (Debian 14.2.0-8) 14.2.0’
• used C++ compiler: ‘g++-14 (Debian 14.2.0-8) 14.2.0’
• 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/1s] OK
• checking whether the package can be unloaded cleanly ... [0s/1s] OK
• checking whether the namespace can be loaded with stated dependencies ... [0s/0s] 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 whether startup messages can be suppressed ... [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 ... [24s/35s] OK
• checking Rd files ... [1s/1s] NOTE checkRd: (-1) ARI.F.Rd:17: Lost braces     17 | \code{ari.f}{Value of the fuzzy adjusted Rand index}        | ^ checkRd: (-1) FKM.gk.Rd:52: Lost braces; missing escapes or markup?     52 | \cr If a cluster covariance matrix becomes singular, then the algorithm stops and the element of \code{value} is {NaN}.        | ^ checkRd: (-1) FKM.gk.ent.Rd:55: Lost braces; missing escapes or markup?     55 | \cr If a cluster covariance matrix becomes singular, the algorithm stops and the element of \code{value} is {NaN}.        | ^ checkRd: (-1) FKM.gk.ent.noise.Rd:57: Lost braces; missing escapes or markup?     57 | \cr If a cluster covariance matrix becomes singular, the algorithm stops and the element of \code{value} is {NaN}.        | ^ checkRd: (-1) FKM.gk.noise.Rd:54: Lost braces; missing escapes or markup?     54 | \cr If a cluster covariance matrix becomes singular, then the algorithm stops and the element of \code{value} is {NaN}.        | ^ checkRd: (-1) FKM.gkb.Rd:55: Lost braces; missing escapes or markup?     55 | \cr If a cluster covariance matrix becomes singular, then the algorithm stops and the element of \code{value} is {NaN}.        | ^ checkRd: (-1) FKM.gkb.ent.Rd:58: Lost braces; missing escapes or markup?     58 | \cr If a cluster covariance matrix becomes singular, the algorithm stops and the element of \code{value} is {NaN}.        | ^ checkRd: (-1) FKM.gkb.ent.noise.Rd:60: Lost braces; missing escapes or markup?     60 | \cr If a cluster covariance matrix becomes singular, the algorithm stops and the element of \code{value} is {NaN}.        | ^ checkRd: (-1) FKM.gkb.noise.Rd:57: Lost braces; missing escapes or markup?     57 | \cr If a cluster covariance matrix becomes singular, then the algorithm stops and the element of \code{value} is {NaN}.        | ^ checkRd: (-1) Fclust.compare.Rd:17: Lost braces     17 | \code{out.index}{Vector containing the similarity measures}        | ^ checkRd: (-1) JACCARD.F.Rd:17: Lost braces     17 | \code{jaccard.f}{Value of the fuzzy Jaccard index}        | ^ checkRd: (-1) RI.F.Rd:17: Lost braces     17 | \code{ri.f}{Value of the fuzzy adjusted Rand index}        | ^ checkRd: (-1) houseVotes.Rd:16: Lost braces     16 | The data collect 1984 United Stated Congressional Voting Records for each of the 435 U.S. House of Representatives Congressmen on the 16 key votes identified by the Congressional Quarterly Almanac (CQA). The variable \code{class} splits the observations in \code{democrat} and \code{republican}. The qualitative variables refer to the votes on \code{handicapped-infants}, \code{water-project-cost-sharing}, \code{adoption-of-the-budget-resolution}, \code{physician-fee-freeze}, \code{el-salvador-aid}, \code{religious-groups-in-schools}, \code{anti-satellite-test-ban}, \code{aid-to-nicaraguan-contras}, \code{mx-missile}, \code{immigration}, \code{synfuels-corporation-cutback}, \code{education-spending}, \code{superfund-right-to-sue}, \code{crime}, \code{duty-free-exports}, and \code{export-administration-act-south-africa}. All these 16 variables are objects of class \code{factor} with three levels according to the CQA scheme: \code{y} refers to the types of votes ''voted for'', ''paired for'' and ''announced for''; \code{n} to ''voted against'', ''paired against'' and ''announced against''; code{yn} to ''voted present'', ''voted present to avoid conflict of interest'' and ''did not vote or otherwise make a position known''.}        | ^
• 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/1s] OK
• checking data for ASCII and uncompressed saves ... 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 examples ... [6s/9s] OK
• checking PDF version of manual ... [8s/11s] OK
• checking HTML version of manual ... [3s/6s] OK
• checking for non-standard things in the check directory ... OK
• DONE

Status: 1 NOTE