Unconfigured Ad

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts
  • jp.
    Senior Member
    • Jul 2013
    • 142

    #16
    Hi
    may I get your views on this thread of my question:
    Discussion of next-gen sequencing related bioinformatics: resources, algorithms, open source efforts, etc





    Originally posted by Helical View Post
    That is strange. When you run cufflinks, are you running it with -g (use reference transcripts and assemble new ones) or -G (only use reference transcripts)? I am no expert but I imagine this error could arise depending on how you mapped to the known transcripts.

    Comment

    • jp.
      Senior Member
      • Jul 2013
      • 142

      #17
      Hi all
      I am having the same problem...
      Warning: couldn't find fasta record for 'NT_166469'! This contig will not be bias corrected.
      Warning: couldn't find fasta record for 'X'!Warning: couldn't find fasta record for 'Y'! This contig will not be bias corrected.
      Initially, I used ensemble ref and got this warning and then I used UCSC genome.fa. Both gives me the same error.
      Why ??

      Originally posted by kmcarr View Post
      Psikon,

      Your hg19 reference file has chromosome names in the format 'chr1' so that is the format they would be in the BAM file(s) generated by TopHat. Whereas the Ensembl GTF you showed in the example has chromosome names as just the numbers (e.g. '11'). Since the alignments in your BAM file(s) are to references named 'chrN' and the annotations in the GTF file are to references named just 'N' Cufflinks naturally won't be able to match them. You need to ensure that the chromosome names in the reference FASTA you use to map exactly match the names in the annotation file. This is typically best done by getting your reference and annotation from the same source.

      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.
        07-01-2026, 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

      ad_right_rmr

      Collapse

      News

      Collapse

      Topics Statistics Last Post
      Started by SEQadmin2, 07-02-2026, 11:08 AM
      0 responses
      9 views
      0 reactions
      Last Post SEQadmin2  
      Started by SEQadmin2, 06-30-2026, 05:37 AM
      0 responses
      13 views
      0 reactions
      Last Post SEQadmin2  
      Started by SEQadmin2, 06-26-2026, 11:10 AM
      0 responses
      20 views
      0 reactions
      Last Post SEQadmin2  
      Started by SEQadmin2, 06-17-2026, 06:09 AM
      0 responses
      54 views
      0 reactions
      Last Post SEQadmin2  
      Working...