Question: bam-readcount does not accept Varscan native format for -l (feature request)
gravatar for Stephane Plaisance
3.1 years ago by
Leuven area (Belgium)
Stephane Plaisance430 wrote:


I painfully discovered that he tutorial using bam-readcount in the CurrProtBioiunfo Varscan 2013 paper is not correct and that one cannot use varscan results but needs instead to provide a 1-based pseudo-BED file as -l input.

I find it not very productive as for indels the generation of such file is not straightforward due to the variable length of sequence inserted or deleted (I read the tip in #93418 producing an arbitrary file +/- 2bps but this is not very clean.

Would it be possible to add an extra argument in parallel of -l to load Varscan native data (not VCF) directly and adapt the coordinates on the fly inside bam-readcount to produce the correct footprint?

Thanks in advance Stephane

varscan2 • 697 views
ADD COMMENTlink written 3.1 years ago by Stephane Plaisance430
# create files with padding of +/-2bps and +/-10bps around the variant positions
gawk 'BEGIN{FS="\t"; OFS="\t"}{print $1, $2-1, $2+2}' varscan_somatic_mpileup_normal-tumor.snp.bed > varscan_somatic_mpileup_normal-tumor.snp.pm2.bed
gawk 'BEGIN{FS="\t"; OFS="\t"}{print $1, $2-9, $2+10}' varscan_somatic_mpileup_normal-tumor.indel.bed > varscan_somatic_mpileup_normal-tumor.indel.pm10.bed
ADD REPLYlink written 3.1 years ago by Stephane Plaisance430
Please log in to add an answer.


Use of this site constitutes acceptance of our User Agreement and Privacy Policy.
Powered by Biostar version 2.3.0
Traffic: 1047 users visited in the last hour