Unconfigured Ad

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts
  • cursecatcher
    Junior Member
    • May 2018
    • 5

    Unable to intersect BAM file with bedtools

    Hi everyone, I'm trying to use bedtools intersect to check the number of mapped reads in target regions (in a .bed file) originated by targeted bisulfite sequencing experiment (EpiSeq Roche).

    I used the following command.

    Code:
    ./bedtools intersect -bed -abam sample2.bam -b 
     ~/Data/MethylSeq/dataset/Agesmoke_dataset/AgeSmkSop_all_primary_targets.bed
    The program terminate with the following message and no result at all.

    Code:
    * WARNING: File sample2.bam has inconsistent naming convention for record:
    NC_000016.9  24163386  24163537  M03971:33:000000000-BN5NL:1:2114:12003:16132/1  255  +
    
    * WARNING: File sample2.bam has inconsistent naming convention for record:
    NC_000016.9  24163386  24163537  M03971:33:000000000-BN5NL:1:2114:12003:16132/1  255  +
    I tried to modify the original SAM file removing the read that cause the problem (that was the first read in the SAM file) and the problem persists with the second read. I tried also the option -nonamecheck with no results.

    Can someone help us? Thank you.
    Nicola
  • Richard Finney
    Senior Member
    • Feb 2009
    • 701

    #2
    Check your chromosome names.
    Are they "chr" style in both bed and bam?

    Comment

    • cursecatcher
      Junior Member
      • May 2018
      • 5

      #3
      Originally posted by Richard Finney View Post
      Check your chromosome names.
      Are they "chr" style in both bed and bam?
      Hi Richard, thanks for the reply.
      About your question, I think not.

      In the bed file I have record like this:
      Code:
      chr1    11123000        11123242        chr1:11123018-11123218
      chr1    16696418        16696674        chr1:16696447-16696647
      while in the SAM file (and consequently in the BAM file) I have record like that:

      Code:
      M03971:33:000000000-BN5NL:1:2114:12003:16132    99      NC_000016.9     24163387        255     151M    =       24163431        194     TGATCGGTGGTGA
      TGGGTTAGGTAGAGTGTATTAGTTCGTTTTTATGTTGTTGATAAAGATATATTCGAGATTGTGTAATTTATGAAAAAGAGGTTTAATGGATTTGGGGAGGTTTTAATTATGGTGGAAGGTTAAAGTTATGTTTTATAT BCCCCCCBBC
      ABGGGGGGFGGGGHHHHFGGHHHHHHHHGGHGGGHHHHHHHHHHHHHHHHHHHHHHHHHHHGHHHHHHHHHHHHHFHHHHGGHHHHHHHHHHHHHHHHGGFGGEHHGHHHHHHHHHHGHHHGHHHHHHHHHHHHHHHHHHH NM:i:1
        ZS:Z:++
      Ps. the SAM file is the result of an alignment with BSMAP.

      Is this the problem? How can I resolve it?
      Nicola

      Comment

      • Richard Finney
        Senior Member
        • Feb 2009
        • 701

        #4
        NC_000016 is a name used for "chr16".
        This the "official" name used at NCBI : https://www.ncbi.nlm.nih.gov/nuccore/NC_000016.10/

        You have to convert the "NCBI name" to "chr" names (or vice versa).

        There are many ways to rename fields. You can always brute force it using a custom simple program or script using your favorite programming language : bash, python, perl, C, etc.

        Any easy way would be to reheader the bam file. Please see samtools documentation for this.

        Comment

        • cursecatcher
          Junior Member
          • May 2018
          • 5

          #5
          Originally posted by Richard Finney View Post
          NC_000016 is a name used for "chr16".
          This the "official" name used at NCBI : https://www.ncbi.nlm.nih.gov/nuccore/NC_000016.10/

          You have to convert the "NCBI name" to "chr" names (or vice versa).

          There are many ways to rename fields. You can always brute force it using a custom simple program or script using your favorite programming language : bash, python, perl, C, etc.

          Any easy way would be to reheader the bam file. Please see samtools documentation for this.
          It works, thank you so much!!
          I'm sorry for the triviality of the problem, but I'm not very practical with this stuff and the bedtools message wasn't very helpful.
          Again, thank you!

          Best regards
          Nicola

          Comment

          Latest Articles

          Collapse

          • GATTACAT
            Reply to Nine Things a Sample Prep Scientist Thinks About Before Sequencing
            by GATTACAT
            Love this - good data definitely starts from good input, and poor input can only give relatively poor data. I particularly like the mention of Nanodrop/absorbance based methods for quantification. It's such a toss up if you'll get an accurate reading or what amounts to a randomly generated number, and a lot of library/sequencing related issues can be traced back to poor quant.
            Today, 11:43 AM
          • SEQadmin2
            Nine Things a Sample Prep Scientist Thinks About Before Sequencing
            by SEQadmin2


            I’m not a sequencing expert. I’m a purification scientist who uses NGS to evaluate workflows my group develops. With this perspective, we think about the sample first and the NGS workflow second. The sequencer is an exceptionally honest reporter, but it can only report on what you give it, so whether you get clean, interpretable data from an NGS workflow is largely determined before you begin.

            Here are nine questions we think about, in roughly the order they matter, before...
            06-18-2026, 07:11 AM
          • SEQadmin2
            From Collection to Sequencing: Why Sample Preparation and Preservation Define Sequencing Data
            by SEQadmin2


            Data variability is still an issue in sequencing technologies despite the advances in reproducibility and accuracy of these platforms. But the problem does not originate in the sequencing itself, but in the previous steps, before the sample reaches the sequencer.


            The first step is collection, followed by preservation and sample preparation for analysis. Most scientists overlook those steps, but not being careful might just be skewing the experiment’s results.
            ...
            06-02-2026, 10:05 AM

          ad_right_rmr

          Collapse

          News

          Collapse

          Topics Statistics Last Post
          Started by SEQadmin2, Yesterday, 05:37 AM
          0 responses
          7 views
          0 reactions
          Last Post SEQadmin2  
          Started by SEQadmin2, 06-26-2026, 11:10 AM
          0 responses
          17 views
          0 reactions
          Last Post SEQadmin2  
          Started by SEQadmin2, 06-17-2026, 06:09 AM
          0 responses
          51 views
          0 reactions
          Last Post SEQadmin2  
          Started by SEQadmin2, 06-09-2026, 11:58 AM
          0 responses
          110 views
          0 reactions
          Last Post SEQadmin2  
          Working...