Converting Probe IDs to HGNC symbols
1
1
Entering edit mode
Manav ▴ 10
@660c5ea3
Last seen 1 day ago
Australia

Hi, I am relatively new to coding, and I am trying to analyse a microarray dataset (GSE37147). I have used GeoQuery to obtain this dataset, and I am trying to convert the probe IDs (e.g. 10000_at) into HGNC symbols for DGE. However, i cant seem to find the correct annotation file with the IDs and gene symbols, nor can I find this specific platform on biomaRt. Any help would be greatly appreciated. Thank You

> gse <- getGEO("GSE37147")
> GSE37147 <- gse[[1]]
> expression_37147 <- exprs(GSE37147)
> expression_37147 <- as.data.frame(expression_37147)
> clinical_37147 <- pData(GSE37147)
> clinical_37147 <- as.data.frame(clinical_37147)
> IDs <- rownames(expression_37147)
> fdata <- fData(GSE37147)
> annotation(GSE37147)
[1] "GPL13243"
Annotation biomaRt GEOquery • 94 views
ADD COMMENT
1
Entering edit mode
@sean-davis-490
Last seen 16 hours ago
United States

The brainarray annotations are very confusing, as the IDs in the fData look like affymetrix probe IDs. To clarify, the brainarray project mapped the original probes to, in this case, Entrez Gene IDs. Therefore, the SPOT_ID column actually represents an Entrez Gene ID. For example, the 10653_at id is mapped to entrez gene 10653. https://www.ncbi.nlm.nih.gov/gene/10653. If you need more information about the genes, you can use the org.hg.eg.db or the EnsemblDB packages, for example. However, now that you have entrez gene ids for each row of your ExpressionSet, you may have all the information you need.

ADD COMMENT
0
Entering edit mode

ah thank u so much

ADD REPLY
0
Entering edit mode

Glad to help. If you ultimately decide that this answers your question, click the checkmark next to the answer. No problem if you don't do so, but it can be a helpful signal to others in the future who have the same or a similar question.

ADD REPLY

Login before adding your answer.

Traffic: 1772 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