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

StrandOps cannot properly handle comparing alleles that use different casing #9

Open
kbeutel opened this issue Nov 28, 2023 · 0 comments

Comments

@kbeutel
Copy link
Contributor

kbeutel commented Nov 28, 2023

StrandOps is setup to handle alleles coded as ATCG or actg but cannot handle matching an upper-cased allele to a lower-cased allele. Both a 'T' and a 't' would be considered valid alleles but not treated as the same allele. This means when determining strand config, an A/G and a/g SNP are not recognized as a match. This issue can be seen when running a gene score pipeline with a .meta file that contains lower-case alleles and study data with upper-case alleles. Error messages such as Alleles in study (T/G) do not match source alleles (t/g) for 3:158126327 appear.

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

No branches or pull requests

1 participant