Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Move non-NCA functions to separate packages #71

Open
billdenney opened this issue Jul 2, 2018 · 1 comment
Open

Move non-NCA functions to separate packages #71

billdenney opened this issue Jul 2, 2018 · 1 comment

Comments

@billdenney
Copy link
Owner

Functions that would make sense to be somewhere else include the following. Ideally, they would find a home in another, more related package. If they won't logically move to another related package that already exists, then a separate package should be created for them.

  • Provenance related
    • addProvenance
    • checkProvenance
  • Averaging related
    • business.mean (and all the functions documented in the business.mean help)
    • geomean, geosd, geocv
  • Rounding related
    • signifString
    • roundString
  • Model-selection related
    • AIC.list
    • get.best.model
    • get.first.model
  • Option handling
    • (not PKNCA.options, but all the supporting functions underneath)
  • formula-related
    • parseFormula
    • formula.parseFormula
@billdenney
Copy link
Owner Author

Option handling may be able to use the settings package.

Formula-related arguments may be easily rewritten to use the Formula package.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant