Unconfigured Ad

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts
  • neokao
    Member
    • Mar 2015
    • 30

    issues of DE genes vs DE transcripts

    I’ve used DESeq, DESeq2 and edgeR for RNAseq DEG analysis (mapped to mouse transcriptome).

    Some little things are really annoying that I thought it should only happen with microarray in the old days.

    For example, I pulled out two RefseqID in my DEGs: NM_001025559 and NM_001025560 (with FDR < 0.05 from all three DESeq, DESeq2 and edgeR packages).
    After I updated them with MGI gene symbol, description, Ensembl gene ID and Entrez Gene ID, it turned out these two RefseqIDs mapped to exact the same MGI gene symbol, description, Ensembl gene ID and Entrez Gene ID.
    I went to NCBI and searched these two RefseqIDs manually and found that they are just two different transcript variants of the same gene.

    I knew for later network analysis, enrichment analysis and pathway analysis, mostly I will need a list of DE genes but not DE transcripts.
    What’s a reasonable way to deal wit this?

    Thanks for your suggestions.
  • dpryan
    Devon Ryan
    • Jul 2011
    • 3478

    #2
    Just quantitate over genes, rather than transcripts. This is simplest with Ensembl's annotation files.

    Comment

    • neokao
      Member
      • Mar 2015
      • 30

      #3
      Originally posted by dpryan View Post
      Just quantitate over genes, rather than transcripts. This is simplest with Ensembl's annotation files.
      Thanks for your reply. Could you shed more light? Do you mean I should use Ensembl annotation file for my reference genome/transcriptome?
      At which step were you suggesting to change?

      I used the UCSC file refMrna.fa as reference transcriptome.
      Then I used bwa for alignment and a perl script to count the reads.

      I finally used the biomaRt package to update my refseqID to MGI symbol, etc.

      useDataset("mmusculus_gene_ensembl",mart=ensembl)

      Thanks.

      Comment

      • dpryan
        Devon Ryan
        • Jul 2011
        • 3478

        #4
        Ah, ditch UCSC and transcriptome alignments. The best method for RNAseq data is to use STAR or HISAT (or tophat2 if you enjoy wasting time) and align to the genome. These tools can be supplied with an annotation file (GTF or GFF format). The resulting SAM/BAM file can then be processed with featureCounts to produce gene-level counts. This is the process I personally use for my mouse datasets and it works quite well. I recommend Ensembl's reference sequence and annotation files, they're more convenient than UCSC's.

        Comment

        • neokao
          Member
          • Mar 2015
          • 30

          #5
          I thought STAR is adapted to align long reads. Mine are short reads. I guess I might be wrong.
          Regarding the Ensembl reference genome/transcriptome for mouse RNAseq, is the Mus_musculus.GRCm38.79.gtf.gz the right one to use for now?

          Thanks.

          Comment

          • dpryan
            Devon Ryan
            • Jul 2011
            • 3478

            #6
            STAR work great with short reads, even small RNAs (e.g. miRNAs).

            Edit: Yes, that's the correct file. Get the fasta file too, since chromosome names differ between Ensembl and UCSC.

            Comment

            • neokao
              Member
              • Mar 2015
              • 30

              #7
              Originally posted by dpryan View Post
              STAR work great with short reads, even small RNAs (e.g. miRNAs).

              Edit: Yes, that's the correct file. Get the fasta file too, since chromosome names differ between Ensembl and UCSC.
              Thanks dpryan. I finally did it with STAR and featurecounts.
              I have some following questions posted with a different topic.

              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
              7 views
              0 reactions
              Last Post SEQadmin2  
              Started by SEQadmin2, 06-30-2026, 05:37 AM
              0 responses
              12 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...