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
Hi, recently I was trying to use Circle-Map to analyze WGS data on GEO. And I got 20 "my_unknown_circle.bed" files following "Identification of circular DNA using Circle Map Realign" tutorial. The whole process was quite smooth. Then I filtered the bed files with the following command:
awk '$5 >1 && $6>50 && $3-$2>10000 && $3-$2<5000000' ../${VAR}_my_unknown_circle.bed > ${VAR}.bed
Among all these ecNDAs, some ecDNAs extensively existed with very high "Circle score". Like this one:
chrX 52857692 55652526 summary.txt
However, their mean coverage was quite low compared with the split and discordant reads. And when I open this interval in UCSC genome Browser (GRCh38), I found that the head and tail DNA sequences were similar if ligated head-to-tail. Is there any chance that Circle-Map may misjudge such junctions in WGS data? And how can I fix such problems?
Many thanks~
The text was updated successfully, but these errors were encountered:
Hi, recently I was trying to use Circle-Map to analyze WGS data on GEO. And I got 20 "my_unknown_circle.bed" files following "Identification of circular DNA using Circle Map Realign" tutorial. The whole process was quite smooth. Then I filtered the bed files with the following command:
awk '$5 >1 && $6>50 && $3-$2>10000 && $3-$2<5000000' ../${VAR}_my_unknown_circle.bed > ${VAR}.bed
Among all these ecNDAs, some ecDNAs extensively existed with very high "Circle score". Like this one:
chrX 52857692 55652526
summary.txt
However, their mean coverage was quite low compared with the split and discordant reads. And when I open this interval in UCSC genome Browser (GRCh38), I found that the head and tail DNA sequences were similar if ligated head-to-tail. Is there any chance that Circle-Map may misjudge such junctions in WGS data? And how can I fix such problems?
Many thanks~
The text was updated successfully, but these errors were encountered: