-
Notifications
You must be signed in to change notification settings - Fork 23
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
CompHet question #138
Comments
Hi Linda, that's currently not allowed. The compound-hets tool assumes a trio (or duo with flag) with unaffected parents. |
Hi Brent,
I can come up with many other variants, but these were the ones that we see all the time. Please let me know if additional examples would be helpful! |
Thank you for the thorough explanation. This helps me to prioritize work. Let me have a look at how to implement this in the next few weeks. It will require substantial changes, so no promises, but you've certainly convinced me of the utility. |
Thanks so much Brent! This is definitely an option that would be helpful for us to use in these contexts! I would assume that others who are working with rare, highly penetrant disorders (with unaffected parents) would be just fine without this cmp het option, and it's these specific scenarios (which depend on your particular family structure and severity/prevalence of the phenotype of interest) where it would be very welcomed! |
Hi Brentp,
I have another question regarding the CompHet tagging. Basically, what you have done in the script has no problem. But in our lab (we are clinical diagnostic lab), we have a bit more relaxed definition of CompHet that even the variant in one parent is Homo change, we would still count the two het variants in the same gene in the kid as CompHet, especially when the gene is in ACMG secondary finding list. Here is one example, the gene HSPG2 is involved in the phenotypes of developmental delayed. And we found:
Using Slivar, the variants in proband were not be tagged as CompHet, but in our case, we consider the variants CompHet because of the gene.
Is there any way we can still utilize your CompHet function to flag the untypical CompHet variants like this? Thank you.
Linda
The text was updated successfully, but these errors were encountered: