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

amrfinder correct for read counts #188

Merged
merged 8 commits into from
Nov 28, 2023

Conversation

andrewdavidsmith
Copy link
Collaborator

  • smithlab_cpp: updating submodule
  • amrfinder: added an option to turn off the correction to likelihood for the number of reads which is applied to the likelihood for the two alleles model
  • EpireadStats.hpp: changing the EpireadStats class to struct and allowing default values for default constructor. Also adding an instance variable to indicate whether log likelihood for allel pair model should correct for number of reads
  • EpireadStats.cpp: adding a variable to control the use of correction to the allele pair model log likelihood based on number of reads
  • amrfinder.cpp: Using the default constructor for EpireadStats
  • amrtester: using an approach more similar to amrfinder which uses the EpireadStats class instance and allows a correction for read count for the allel pair model log likelihood
  • amrtester: more changes
  • md5sum: update for the empty amr file output by amrfinder currently

…or the number of reads which is applied to the likelihood for the two alleles model
…ing default values for default constructor. Also adding an instance variable to indicate whether log likelihood for allel pair model should correct for number of reads
…to the allele pair model log likelihood based on number of reads
… EpireadStats class instance and allows a correction for read count for the allel pair model log likelihood
@andrewdavidsmith andrewdavidsmith merged commit b6c2b07 into master Nov 28, 2023
1 check passed
@andrewdavidsmith andrewdavidsmith deleted the amrfinder-correct-for-read-counts branch November 28, 2023 03:41
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.

1 participant