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
I am wondering whether there are any limitations on its detection length.
Could I use strspy to detect the repeat sequence CCCCGCGCCCGGCCTTCCCCGGGGTCCCTGCGGCCCCGACTGTGCGCC profile?
How do I use strspy to quantify the number of contiguous repeat units? I did not see a direct result from the output, or I might have missed this information.
Besides, when running strspy, I got this error:
***** WARNING: File /scratch/kinfai_root/kinfai0/hsinlun/tri_test/align/C9ORF72_1_9R_NanoSim_2x.sorted.bam has inconsistent naming convention for record:
chr1 14337 20040 C9ORF72-1_14451_aligned_12683_F_19_5702_13 0 +
***** WARNING: File /scratch/kinfai_root/kinfai0/hsinlun/tri_test/align/C9ORF72_1_9R_NanoSim_2x.sorted.bam has inconsistent naming convention for record:
chr1 14337 20040 C9ORF72-1_14451_aligned_12683_F_19_5702_13 0 +
I would appreciate any solutions to this.
Best,
Hsin
The text was updated successfully, but these errors were encountered:
There is no limitation of length of the STRs. We have seen STR in chrY more than 100.
You can, but STRspy rely on the database fasta (flanking_seq -----STR repeats------flanking)and the bed. If you are able to prepare from your reference location (repeat ordinates).
if you provide the db fasta, STRspy will output a freq files of all STRs that present in your sample. Please have a look the test db fasta and the results.
It would be useful to track the warning or error if you show me how did you run the STRspy step by step. But i guess thats the error comes from SNV calling tool i.e. xAtlas. It happens as your bam is the matching the reference.
xAtlas, require the str bam not the genomic bam.
Hi Rupesh,
I have several questions about the usage:
CCCCGCGCCCGGCCTTCCCCGGGGTCCCTGCGGCCCCGACTGTGCGCC
profile?Besides, when running strspy, I got this error:
I would appreciate any solutions to this.
Best,
Hsin
The text was updated successfully, but these errors were encountered: