Code review issues

[billdenney]

Some aspects I noticed that I noticed in the original code that I am not sure if they are intentional:

• pk.calc.sparse_auc has a method argument that is not used, because the method for pk.calc.auc is always fixed to linear

• I get uncovered warnings in the tests that may be related with Warn on use of PKNCA.set.summary(reset=TRUE) #478:

Warning message:
In PKNCA.set.summary(reset = TRUE) :
  `reset = TRUE` is not intended for general use, summary() may not work after resetting summary instructions

Originally posted by @Gero1999 in #469 (comment)

[billdenney]

• pk.calc.sparse_auc has a method argument that is not used, because the method for pk.calc.auc is always fixed to linear

This is semi-intentional. It is intentional in that it matches the call format of all the other AUC functions. But sparse AUC is only allowed for linear trapezoidal rule as the underlying statistics have not been worked out for methods that include log interpolation. It would be best to make sure that there is a test for the method argument to be sure that it is always linear (but keep the argument). Could you make that testing as a PR?

[billdenney]

• I get uncovered warnings in the tests that may be related with Warn on use of PKNCA.set.summary(reset=TRUE) #478:

Warning message:
In PKNCA.set.summary(reset = TRUE) :
  `reset = TRUE` is not intended for general use, summary() may not work after resetting summary instructions

I would guess that those are intended uses in the tests so that we can test different summaries being created correctly. Could you please make a PR that suppresses those warnings where they appear to be intentional?