CRAN messages

gistfile1.txt

* checking S3 generic/method consistency ... WARNING
profile:
  function(fitted, ...)
profile.by.group:
  function(x, y, original.names, profile.plot, ...)

profile:
  function(fitted, ...)
profile.reliability:
  function(form1, form2)

See section ‘Generic functions and methods’ of the ‘Writing R
Extensions’ manual.

* checking R code for possible problems ... NOTE
profile.by.group: warning in axis(1, at = 1:k, lab = labs): partial
  argument match of 'lab' to 'labels'
profile.by.group: warning in pf(F1 * (c1 + c2 - k)/(c1 + c2 - 2)/(k -
  1), k - 1, (c1 + c2 - k), lower = F): partial argument match of
  'lower' to 'lower.tail'
profile.by.group: warning in pf(F2, 1, (c1 + c2 - 2), lower = F):
  partial argument match of 'lower' to 'lower.tail'
profile.by.group: warning in pf(F3 * (c1 + c2 - k + 1)/(c1 + c2 - 1)/(k
  - 1), (k - 1), (c1 + c2 - k + 1), lower = F): partial argument match
  of 'lower' to 'lower.tail'
print.critpat: no visible binding for global variable ‘object’

* checking for code/documentation mismatches ... WARNING
Codoc mismatches from documentation object 'profileplot':
profileplot
  Code: function(form, person.id, interval = 10, by.pattern = TRUE,
                 original.names = TRUE)
  Docs: function(form, person.id, interval = 10)
  Argument names in code not in docs:
    by.pattern original.names

* checking Rd \usage sections ... NOTE
S3 methods shown with full name in documentation object 'profile.by.group':
  ‘profile.by.group’

S3 methods shown with full name in documentation object 'profile.reliability':
  ‘profile.reliability’

The \usage entries for S3 methods should use the \method markup and not
their full name.

WARNING: There were 2 warnings.
NOTE: There were 2 notes.
See
  ‘/Users/chris/build/profileRbuild/profileR.Rcheck/00check.log’
for details.