* using log directory ‘/srv/hornik/tmp/CRAN/NMRphasing.Rcheck’
* using R Under development (unstable) (2023-09-26 r85226)
* using platform: x86_64-pc-linux-gnu
* R was compiled by
    Debian clang version 16.0.6 (15)
    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 ‘NMRphasing/DESCRIPTION’ ... OK
* checking extension type ... Package
* this is package ‘NMRphasing’ version ‘0.0.2’
* package encoding: UTF-8
* checking CRAN incoming feasibility ... [3s/3s] WARNING
Maintainer: ‘Aixiang Jiang <aijiang@bccrc.ca> <aixiang.jiang@pathology.ubc.ca>’

The maintainer field is invalid or specifies more than one person

New submission

Possibly misspelled words in DESCRIPTION:
  NMR (3:62)

Package has a VignetteBuilder field but no prebuilt vignette index.

The Title field should be in title case. Current version is:
‘Phase error correction and baseline correction for 1D NMR data’
In title case that is:
‘Phase Error Correction and Baseline Correction for 1d NMR Data’

The Description field should not start with the package name,
  'This package' or similar.

This build time stamp is over a month old.

Found the following \keyword or \concept entries
which likely give several index terms:
  File ‘MPC_DAOM.Rd’:
    \keyword{NMR,}
  File ‘MPC_EMP.Rd’:
    \keyword{NMR,}
  File ‘NLS.Rd’:
    \keyword{NMR,}
  File ‘NMRphasing.Rd’:
    \keyword{NMR,}
  File ‘SPC_AAM.Rd’:
    \keyword{NMR,}
  File ‘SPC_DAOM.Rd’:
    \keyword{NMR,}
  File ‘SPC_DSM.Rd’:
    \keyword{NMR,}
  File ‘SPC_EMP.Rd’:
    \keyword{NMR,}
* 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 ‘NMRphasing’ can be installed ... [1s/1s] OK
* checking package directory ... OK
* checking for future file timestamps ... OK
* checking DESCRIPTION meta-information ... OK
* checking top-level files ... NOTE
Non-standard files/directories found at top level:
  ‘README.rmd’ ‘README_files’ ‘docs’
* 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 ... [0s/0s] OK
* checking whether the package can be loaded with stated dependencies ... [0s/0s] OK
* checking whether the package can be unloaded cleanly ... [0s/0s] 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 ... [0s/0s] 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 ... [3s/3s] NOTE
DAOM: no visible global function definition for ‘optim’
EMP: no visible global function definition for ‘optim’
HilbertWithFT: no visible global function definition for ‘fft’
SPC_AAM: no visible global function definition for ‘optim’
SPC_DAOM: no visible global function definition for ‘optim’
SPC_DSM: no visible global function definition for ‘optim’
SPC_EMP: no visible global function definition for ‘optim’
myBaseline: no visible global function definition for ‘lowess’
myBaseline: no visible global function definition for ‘lm’
Undefined global functions or variables:
  fft lm lowess optim
Consider adding
  importFrom("stats", "fft", "lm", "lowess", "optim")
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 ... OK
* checking Rd \usage sections ... OK
* checking Rd contents ... OK
* checking for unstated dependencies in examples ... OK
* checking LazyData ... NOTE
  'LazyData' is specified without a 'data' directory
* checking examples ... NONE
* checking PDF version of manual ... [2s/2s] OK
* checking HTML version of manual ... [0s/0s] OK
* checking for code which exercises the package ... WARNING
No examples, no tests, no vignettes
* checking for non-standard things in the check directory ... OK
* checking for detritus in the temp directory ... OK
* DONE
Status: 2 WARNINGs, 3 NOTEs