-
Notifications
You must be signed in to change notification settings - Fork 0
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
small functionality patches to strand flip checks, dosage calculator, automated statistics #70
base: main
Are you sure you want to change the base?
Conversation
@@ -31,12 +31,16 @@ convert.alleles.to.pgs.dosage <- function(called.alleles, risk.alleles) { | |||
} else { | |||
# check that called.alleles is a vector of genotypes in allelic notation or '.' separated by a slash or pipe | |||
# "*" characters represent overlapping deletions from an upstream indel and are accepted VCF format | |||
allowed.pattern <- '^((([A-Z]+|\\.|\\*)[/\\|]([A-Z]+|\\.|\\*))|\\.)$' # '|' are special chars in regular expressions | |||
allowed.pattern <- '^((([A-Z]+|\\.|\\*)[/\\|]([A-Z]+|\\.|\\*))|\\.|[A-Z]+)$' # '|' are special chars in regular expressions |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You have some comments here about what individual characters mean. Is it possible to include an entire example? I think it would be helpful for interpretation.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Left a comment for you to think about, but otherwise LGTM!
Updates to strand flip checker functionality when handling INDELs: mark INDEL effect switches as "effect _switch"
Updates to dosage calculator to handle hemizygous genotypes: single alleles added to allowed allele format list, single alleles evaluated with haploid dosage (+ unit tests).
Updates to
apply.polygenic.score
to more carefully filter data for statistical analyses.Update version to 3.0.1 (no breaking changes)
I have read the code review guidelines and the code review best practice on GitHub check-list.
The name of the branch is meaningful and well formatted following the standards, using [AD_username (or 5 letters of AD if AD is too long)-[brief_description_of_branch].
I have set up or verified the branch protection rule following the github standards before opening this pull request.
I have added the changes included in this pull request to
NEWS
under the next release version or unreleased, and updated the date.I have updated the version number in
metadata.yaml
andDESCRIPTION
.Both
R CMD build
andR CMD check
run successfully.Closes #...
Testing Results
All unit tests pass.