fxn naming to comply with ROpenSci norms about birdsize HOT 1 CLOSED

populations, communities, species...individuals

I hesitate to make these classes, but for function naming at least:

User facing functions

• species (could use sp_* but there's the whole sp lexicon):
  • get parameters (species_define) is a wrapper for
    - lookup parameters (species_lookup)
    - estimate parameters (species_estimate)
• populations
  • the core fxionality of this package is to generate population-wide size estimates (pop_generate)
  • combining over populations gets you to community estimates? (pop_combine)
• communities
  • fxns not implemented yet
  • but, iterate over species to simulate populations
  • fxns to operate on communities should apply naturally to BBS survey routes as imported using rdataretriever
  • clean data following BBS norms (comm_clean)
  • generate population estimates for a community (comm_generate)
  • generate state variable tallies for a community (comm_summarize)
• estimate_bmr I feel like should be user-facing, but it's kind of free-floating (technically it applies to individuals)

Under-the-hood functions

• Stuff to calculate the scaling relationship - included for reproducibility/transparency
• Lookup/estimate utilities
• ind_draw: actual random number generator that works on individuals; not user-facing
• ind_energy: could use this so that estimate_b fits convention but that's getting pretty fine

from birdsize.