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

Rarefaction as optional strategy for alpha diversity #417

Closed
antagomir opened this issue Aug 10, 2023 · 2 comments · Fixed by #460
Closed

Rarefaction as optional strategy for alpha diversity #417

antagomir opened this issue Aug 10, 2023 · 2 comments · Fixed by #460

Comments

@antagomir
Copy link
Member

Ref: Pat Schloss' recent analyses on rarefaction in alpha & beta diversity. This addressess well some of the long debates and controversies surrounding rarefaction in microbial ecology.

Based on this I tend to think that rarefaction should be provided as an option for alpha diversity calculations.

Here rarefaction refers to averaging alpha diversity estimates across many random rarifications (100x and 1000x are used in the preprint). This makes most difference in less diverse and low abundance environments but may influence also more rich ecosystems (see the preprint).

Options:

  • write an apply/do loop around estimateDiversity and just provide that as an example in mia vignette / OMA
  • provide rarefaction as an option in estimateDiversity directly (including user defined arguments for the number of rarification rounds, and for the read count threshold with some automated default such as the smallest read count among samples)

I am in favour of the second option.

Note:

  • we have estimateDiversity, estimateRichness, estimateDominance etc.; these all should be updated
  • or we can consider combining them into a single estimateAlpha function to simplify procedures and maintenance (perhaps a separate issue to deal with first to minimze extra work)
@ChouaibB
Copy link
Contributor

I agree with the second option and then still show an example at vignette and/or OMA for example.
Would for instance estimateAlphaWithRarefaction be a better naming? upon which the function would take as argument the functions: estimateDiversity, estimateRichness, estimateDominance?

@ChouaibB ChouaibB linked a pull request Oct 13, 2023 that will close this issue
@antagomir
Copy link
Member Author

Lets do: "estimateAlpha" at least for now

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

Successfully merging a pull request may close this issue.

3 participants