* using log directory 'd:/Rcompile/CRANpkg/local/4.6/NMA.Rcheck'
* using R version 4.6.1 (2026-06-24 ucrt)
* using platform: x86_64-w64-mingw32
* R was compiled by
    gcc.exe (GCC) 14.3.0
    GNU Fortran (GCC) 14.3.0
* running under: Windows Server 2022 x64 (build 20348)
* using session charset: UTF-8
* current time: 2026-08-12 08:33:07 UTC
* checking for file 'NMA/DESCRIPTION' ... OK
* checking extension type ... Package
* this is package 'NMA' version '3.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 hidden files and directories ... OK
* checking for portable file names ... OK
* checking whether package 'NMA' can be installed ... OK
* checking installed package size ... OK
* checking package 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 ... OK
* checking R files for syntax errors ... OK
* checking whether the package can be loaded ... [3s] OK
* checking whether the package can be loaded with stated dependencies ... [3s] OK
* checking whether the package can be unloaded cleanly ... [3s] OK
* checking whether the namespace can be loaded with stated dependencies ... [3s] OK
* checking whether the namespace can be unloaded cleanly ... [3s] OK
* checking loading without being on the library search path ... [3s] 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 ... [27s] OK
* checking Rd files ... [1s] OK
* checking Rd metadata ... 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] OK
* checking LazyData ... OK
* checking data for ASCII and uncompressed saves ... OK
* checking examples ... [34s] OK
* checking PDF version of manual ... [20s] OK
* checking HTML version of manual ... [7s] OK
* DONE
Status: OK

Check process probably crashed or hung up for 20 minutes ... killed
Most likely this happened in the example checks (?),
if not, ignore the following last lines of example output:
    1-6 3 16800 2001.767 1997 2005
    6-7 2 27357 2001.807 2000 2003
  3-6-8 1 33357 2002.000 2002 2002
    4-5 1  9193 2002.000 2002 2002
    3-8 1  6083 2003.000 2003 2003
    4-6 1 15245 2004.000 2004 2004
    5-6 1 19257 2005.000 2005 2005
    4-7 2  5129 2006.201 2005 2007
    1-4 2  7439 2006.576 2001 2008
    1-8 1  3845 2008.000 2008 2008
    3-4 1 17118 2008.000 2008 2008

> 
> 
> 
> ### * <FOOTER>
> ###
> cleanEx()
> options(digits = 7L)
> base::cat("Time elapsed: ", proc.time() - base::get("ptime", pos = 'CheckExEnv'),"\n")
Time elapsed:  32 1.22 33.24 NA NA 
> grDevices::dev.off()
null device 
          1 
> ###
> ### Local variables: ***
> ### mode: outline-minor ***
> ### outline-regexp: "\\(> \\)?### [*]+" ***
> ### End: ***
> quit('no')
======== End of example output (where/before crash/hang up occured ?) ========