Comments (3)
In genomewide more, off-target regions are not scanned. So that shouldn't change anything.
This regions seems a bit odd. It seems to have a massively inflated coverage, while it seems like there are a lot of mismatches in the aligned reads. While a large expansion could cause a fairly large inflation in coverage, it's also possible that this region is poorly assembled in the reference. We identified quite a few of these on hg19.
If you have other samples, you can compare the estimate on the same locus across samples. If it is called as expanded across your cohort, it's likely caused by an issue in the reference, and you can confidently filter this locus out.
Hope this helps! :)
from gangstr.
Hi Matthias,
Thanks for reporting this issue.
Do you have off-target regions specified in your bed file?
Regardless of that, if you use --genomewide, the off-target regions should not be scanned.
I advise checking the loci that seem to be problematic in IGV. Sometimes the flanking region around a STR locus looks similar to imperfect copies of the motif. This can cause inflation in the estimate for that region. In that case, the best approach is to not included those loci, as GangSTR requires the flanking region to be non-repetitive.
Hope this helps.
Best,
Nima
from gangstr.
Hi Nima,
Thanks for your answer.
I did not specify any off-target regions in my bed file yet. If that might help I would like to try that though. Do you have a recommendation on how to go about that? Would you recommend specifying all regions with the same motif for each locus or filtering them by read depth or something similar and add a subset as off-target regions to all other loci?
I already checked some of the loci in IGV and the flanking regions did not look particularly similar to the repeat.
Eg:
Thanks,
Matthias
from gangstr.
Related Issues (20)
- Interesting Compiling issue HOT 6
- GangSTR fails on small input files HOT 3
- GangSTR --help outputs error
- Downstream filtering for haploid TRs HOT 4
- str::out_of_range HOT 2
- [GangSTR-2.5.0] ERROR: Error extracting read length HOT 8
- Read group HOT 1
- genome index HOT 1
- Warning in Gangstr run HOT 3
- Help with understanding GGL values HOT 4
- HELP HOT 3
- error after trimming sequences
- Issue about "Not enough reads extracted. Skipping locus.." HOT 1
- MarkDuplicates reads filter
- Support for unequal read lengths in BAM
- Alleles reported as numbers rather than bases in output VCF
- Allowing mismatch in Long str
- Help : Genotyping vcf results (loci call & Realignment resutls)
- local realignment in GangSTR
- generate str_info_file
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from gangstr.