* using log directory ‘/srv/hornik/tmp/CRAN_pretest/mlspatial.Rcheck’ * using R Under development (unstable) (2025-07-08 r88392) * using platform: x86_64-pc-linux-gnu * R was compiled by Debian clang version 19.1.7 (3) Debian flang-new version 19.1.7 (3) * running under: Debian GNU/Linux 13 (trixie) * using session charset: UTF-8 * checking for file ‘mlspatial/DESCRIPTION’ ... OK * this is package ‘mlspatial’ version ‘0.1.0’ * package encoding: UTF-8 * checking CRAN incoming feasibility ... [3s/4s] NOTE Maintainer: ‘Adeboye Azeez ’ New submission * 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 ‘mlspatial’ can be installed ... [4s/4s] OK * 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 code files for non-ASCII characters ... WARNING Found the following file with non-ASCII characters: R/model_evaluation.R Portable packages must use only ASCII characters in their R code and NAMESPACE directives, except perhaps in comments. Use \uxxxx escapes for other characters. Function ‘tools::showNonASCIIfile’ can help in finding non-ASCII characters in files. * 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 ... [0s/0s] OK * checking whether the namespace can be unloaded cleanly ... [0s/0s] OK * checking loading without being on the library search path ... [1s/1s] OK * checking use of S3 registration ... OK * checking dependencies in R code ... WARNING '::' or ':::' imports not declared from: ‘methods’ ‘xgb’ Package in Depends field not imported from: ‘tidyverse’ These packages need to be imported from (in the NAMESPACE file) for when this namespace is loaded but not attached. * checking S3 generic/method consistency ... OK * checking replacement functions ... OK * checking foreign function calls ... OK * checking R code for possible problems ... [2s/2s] NOTE compute_spatial_autocorr: no visible global function definition for ‘%>%’ eval_model: no visible global function definition for ‘model.matrix’ eval_model: no visible global function definition for ‘predict’ join_data: no visible global function definition for ‘%>%’ plot_obs_vs_pred: no visible global function definition for ‘aes’ plot_obs_vs_pred: no visible binding for global variable ‘obs’ plot_obs_vs_pred: no visible binding for global variable ‘pred’ plot_obs_vs_pred: no visible global function definition for ‘geom_point’ plot_obs_vs_pred: no visible global function definition for ‘geom_abline’ plot_obs_vs_pred: no visible global function definition for ‘labs’ plot_obs_vs_pred: no visible global function definition for ‘theme_minimal’ plot_single_map: no visible global function definition for ‘tm_shape’ plot_single_map: no visible global function definition for ‘tm_fill’ plot_single_map: no visible global function definition for ‘tm_scale_intervals’ plot_single_map: no visible global function definition for ‘tm_legend’ plot_single_map: no visible global function definition for ‘tm_borders’ plot_single_map: no visible global function definition for ‘tm_compass’ plot_single_map: no visible global function definition for ‘tm_layout’ train_xgb: no visible global function definition for ‘model.matrix’ train_xgb: no visible global function definition for ‘xgb.DMatrix’ Undefined global functions or variables: %>% aes geom_abline geom_point labs model.matrix obs pred predict theme_minimal tm_borders tm_compass tm_fill tm_layout tm_legend tm_scale_intervals tm_shape xgb.DMatrix Consider adding importFrom("stats", "model.matrix", "predict") to your NAMESPACE file. * checking Rd files ... [0s/0s] 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 ... WARNING Data codoc mismatches from Rd file 'panc_incidence.Rd': Variables in data frame 'panc_incidence' Code: NAME agea ageb agec fagea fageb fagec female incidence magea mageb magec male yra yrb yrc yrd yre Docs: NAME agea ageb agec fagea fageb fagec female incidence magea mageb mageb male yra yrb yrc yrd yre Data codoc mismatches from Rd file 'panc_prevalence.Rd': Variables in data frame 'panc_prevalence' Code: NAME agea ageb agec fagea fageb fagec female magea mageb magec male prevalence yra yrb yrc yrd yre Docs: NAME agea ageb agec fagea fageb fagec female magea mageb mageb male prevalence yra yrb yrc yrd yre Data codoc mismatches from Rd file 'pancre_mort.Rd': Variables in data frame 'pancre_mort' Code: NAME agea ageb agec fagea fageb fagec female magea mageb magec male mortality yra yrb yrc yrd yre Docs: NAME agea ageb agec fagea fageb fagec female magea mageb mageb male mortality yra yrb yrc yrd yre * checking Rd \usage sections ... WARNING Undocumented arguments in Rd file 'compute_spatial_autocorr.Rd' ‘sf_data’ ‘values’ ‘signif’ Undocumented arguments in Rd file 'eval_model.Rd' ‘model’ ‘data’ ‘formula’ ‘model_type’ Undocumented arguments in Rd file 'plot_obs_vs_pred.Rd' ‘observed’ ‘predicted’ ‘title’ Undocumented arguments in Rd file 'train_rf.Rd' ‘data’ ‘formula’ ‘ntree’ ‘seed’ Undocumented arguments in Rd file 'train_svr.Rd' ‘data’ ‘formula’ Undocumented arguments in Rd file 'train_xgb.Rd' ‘data’ ‘formula’ ‘nrounds’ ‘max_depth’ ‘eta’ 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. * 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 installed files from ‘inst/doc’ ... OK * checking files in ‘vignettes’ ... OK * checking examples ... NONE * checking for unstated dependencies in ‘tests’ ... OK * checking tests ... [1s/1s] OK Running ‘testthat.R’ [1s/1s] * checking for unstated dependencies in vignettes ... OK * checking package vignettes ... OK * checking re-building of vignette outputs ... [34s/34s] OK * checking PDF version of manual ... [3s/3s] OK * checking HTML version of manual ... [0s/0s] OK * checking for non-standard things in the check directory ... OK * checking for detritus in the temp directory ... OK * DONE Status: 4 WARNINGs, 2 NOTEs