Skip to content

Kraken2 depletion for human reads as alternative to bmtagger #938

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

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

yesimon
Copy link
Contributor

@yesimon yesimon commented Mar 8, 2019

  • Add kraken_unclassified command that combines p filtering with depletion
  • Less sensitive than bmtagger (tradeoffs) but much faster. Can be controlled with p. p=0.01-0.05 a
    close to bmtagger but not as aggressive.
  • Custom kraken2 needed to avoid executable name clashes with other kraken* packages.

@tomkinsc
Copy link
Member

Does it make any sense to use this as a first pass to pare down data prior to running bmtagger?

@yesimon
Copy link
Contributor Author

yesimon commented Mar 29, 2019

Not really because bmtagger is already fast enough. It's not going to deplete as many reads as bmtagger.

Add support for krakenuniq, kaiju to replace kraken and diamond in
default pipelines.

Both rely on customized krakenuniq/kaiju packages for custom
functionality, like loading database
from pipe or printing out all taxa hits (kaiju).

Krona fixed to use hit counts as scores in report files directly,
instead of counting the
individual read classifications (which takes a long time).
@yesimon yesimon force-pushed the sy-kraken2-deplete branch from fb24932 to 7126fa0 Compare April 12, 2019 03:19
@yesimon yesimon force-pushed the sy-kraken2-deplete branch from 7126fa0 to b930c7b Compare April 19, 2019 14:48
* Add kraken_unclassified command that combines p filtering with depletion
* Less sensitive than bmtagger (tradeoffs) but much faster. Can be controlled with p. p=0.01-0.05 a
  close to bmtagger but not as aggressive.
* Custom kraken2 needed to avoid executable name clashes with other kraken* packages.
@yesimon yesimon force-pushed the sy-kraken2-deplete branch from b930c7b to 2237822 Compare April 19, 2019 14:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants