Unconfigured Ad

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts
  • ykdang
    Junior Member
    • Oct 2011
    • 7

    chrom file format problem with bedtools genomecov

    Hi,
    I am new to bioinformatics. I am trying to use the genomecov in the bedtools into bedgraph, which I want to load them onto genome browser. Overal it works perfect with ChIP-seq data, which is non-stranded. However, when I try to do it with HITS-CLIP or RNA-seq, which are strand-specific, it shows the error message
    *****ERROR: Unrecognized parameter: NC10.chrom *****
    I looked into the chrom file, which is like this
    supercont10.1 9798893
    supercont10.2 4478683
    supercont10.3 5274802
    supercont10.4 6000761
    supercont10.5 6436246
    supercont10.6 4218384
    supercont10.7 4255303
    supercont10.8 192308
    supercont10.9 142473
    supercont10.10 125404
    supercont10.11 31696
    supercont10.12 19714
    supercont10.13 13515
    supercont10.14 11565
    supercont10.15 9397
    supercont10.16 8983
    supercont10.17 6701
    supercont10.18 6309
    supercont10.19 4755
    supercont10.20 1646

    I don't know why when I added the option "-strand" then the program refuse to recognize the chorm file, though genomecov does accept it with the sample bam file when "-strand" are deleted.
    Any suggestion are greatly appreciated!!
  • ykdang
    Junior Member
    • Oct 2011
    • 7

    #2
    just add more information for troubleshooting

    I attached all the processes I did from begining for the HITS-CLIP

    tophat -p 8 -G NC10_transcripts.gff3 -o wt_output --library-type=fr-secondstrand <genome_indexes> wt.fq

    next, I sort the bam and calculate the coverage. the command is

    samtool sort accepted_hits.bam sorted.bam
    genomeCoverageBed -ibam <sorted.bam> -strand -bg -g NC10.chrom > output.bg

    then I got the error message

    *****ERROR: Unrecognized parameter: NC10.chrom *****

    Comment

    • TiborNagy
      Senior Member
      • Mar 2010
      • 329

      #3
      You are use the wrong command line order:
      genomeCoverageBed -ibam -strand -bg -i <sorted.bam> -g NC10.chrom

      Comment

      • ykdang
        Junior Member
        • Oct 2011
        • 7

        #4
        It work now. But patially right. My bam file is acutally strand-specific pair-end sequencing. After calculate the coverage from each strand and merge them, I found that all gene has antisense transcripts, which should be wrong. I guess the genomecov might also count the mate of read from the opposite strand. Do you know how to fix this? Thanks!

        Comment

        Latest Articles

        Collapse

        • SEQadmin2
          Advanced Sequencing Platforms Tackle Neuroscience’s Toughest Genomics Problems
          by SEQadmin2



          Genomics studies in neuroscience face a special challenge due to the brain’s complexity and scarcity of samples. Mapping changes in cell type and state using conventional next-generation sequencing methods remains challenging. Advances in technologies like single-cell sequencing, spatial transcriptomics, and long-read sequencing have opened the door to deeper studies of the brain and diseases like Alzheimer’s, amyotrophic lateral sclerosis (ALS), and schizophrenia.
          ...
          07-09-2026, 11:10 AM
        • SEQadmin2
          Cancer Drug Resistance: The Lingering Barrier to Rising Survival
          by SEQadmin2



          Cancer survival rates have significantly increased in the last few decades in the United States, reaching a combined 70% 5-year survival rate by 2021. Behind this number, there are years of research to find new therapies, drug targets, and early detection methods. But there is one core challenge that keeps slowing down these advances, and it’s about drug resistance.

          There is no single reason why many patients don’t respond to treatment as expected. Cancer is...
          07-08-2026, 05:17 AM
        • 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.
          07-01-2026, 11:43 AM

        ad_right_rmr

        Collapse

        News

        Collapse

        Topics Statistics Last Post
        Started by SEQadmin2, 07-13-2026, 10:26 AM
        0 responses
        27 views
        0 reactions
        Last Post SEQadmin2  
        Started by SEQadmin2, 07-09-2026, 10:04 AM
        0 responses
        37 views
        0 reactions
        Last Post SEQadmin2  
        Started by SEQadmin2, 07-08-2026, 10:08 AM
        0 responses
        24 views
        0 reactions
        Last Post SEQadmin2  
        Started by SEQadmin2, 07-07-2026, 11:05 AM
        0 responses
        34 views
        0 reactions
        Last Post SEQadmin2  
        Working...