You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As a junior researcher aiming to improve my skills in the field of bioinformatics, I have encountered an issue while utilizing xTEA's case-control mode to identify possible somatic transposon insertions. When I checked the resulting regions in IGV, in several regions, I found the control samples exhibit longer and more clipped reads compared to the case samples. What could be the reason for this? As an example, I am dropping screenshots from the IGVs.
Would you kindly help me to find a potential solution to my problem?
Many thanks for considering my request.
The text was updated successfully, but these errors were encountered:
Based on our findings, the allele frequency in the tumor (case) and matched normal (control) samples was determined to be 0.545. How should we interpret an allele frequency of 0.545 in the context of potential allele dropout? Specifically, can we conclude that despite possible allele dropout in the tumor sample, there is an insertion in the region? Or should this insertion in the tumor sample only be considered a sequencing artifact?
It's a germline insertion. That's why you observed it in both the case and control. I mean in the tumor sample, there is an allele dropout, thus the VAF is lower than in the control.
Hello,
Thanks for developing xTEA.
As a junior researcher aiming to improve my skills in the field of bioinformatics, I have encountered an issue while utilizing xTEA's case-control mode to identify possible somatic transposon insertions. When I checked the resulting regions in IGV, in several regions, I found the control samples exhibit longer and more clipped reads compared to the case samples. What could be the reason for this? As an example, I am dropping screenshots from the IGVs.
Would you kindly help me to find a potential solution to my problem?
Many thanks for considering my request.
The text was updated successfully, but these errors were encountered: