Converting gene_ids from GTF file to common gene symbols
1
0
Entering edit mode
5 hours ago
Gus • 0

Hi All,

Long time reader, first-time posting. I have been doing RNA-seq analysis for some time now on non-model species. My pipeline was:

  1. Trim and filter reads with bbduk and trimmomatic
  2. Align to genome with HISAT2
  3. Generate counts with featureCounts
  4. Export counts table and load into R for DEG analysis in EdgeR

I currently have gene count tables that have 1 row for each gene id as it appears in the GTF file (taken from NCBI). The problem is that for one species, Chaenocephalus aceratus, all the gene IDs are really locus tags, and products are listed as hypothetical proteins. I would like to be able to compare expression across all species for common genes. But to do this I need to convert these species-specific gene IDs to more common gene symbols.

I also have a mapping file which contains the protein accession IDs. But this species isn't found on common solutions like David, Entrez, Ensemble, etc.

I also have created a fasta file which contains the genome sequences for all the CDS regions in the GTF file, organized by gene id (locus tags). But I'm unsure how I might use these to identify the genes / create a mapping list for gene ontology analysis, etc.

Any help would be greatly appreciated! I'm posting from my phone, but can provide more specific code snippets / examples as needed.

Thanks!

gene_id GTF symbol • 71 views
ADD COMMENT
0
Entering edit mode
3 hours ago
LChart 4.5k

I believe Ensembl uses GenBlast for this purpose - GenBlasting mammalian SwissProt against the reference genome with exon repair turned on to identify genes with cutoffs probably 50% coverage and 50% identity and 5% evalue. You have a gene build already, so you could probably use blastx directly against uniprot/swissprot.

ADD COMMENT

Login before adding your answer.

Traffic: 2655 users visited in the last hour
Help About
FAQ
Access RSS
API
Stats

Use of this site constitutes acceptance of our User Agreement and Privacy Policy.

Powered by the version 2.3.6