Problem with hgu133a
1
0
Entering edit mode
@colin-a-smith-325
Last seen 9.6 years ago
Germany
There appears to be a problem with the Gene Ontology metadata in hgu133a: > library(hgu133a) > get("GO:0000002", hgu133aGO2ALLPROBES) [1] "93062_at" "161630_i_at" "96296_at" "100040_at" > get("93062_at", hgu133aGO) Error in get(x, envir, mode, inherits) : variable "93062_at" was not found > hgu133a() Quality control information for hgu133a Date built: Thu Jun 26 13:35:54 2003 Number of probes: 22283 Probe number missmatch: None Probe missmatch: None Mappings found for probe based rda files: hgu133aACCNUM found 22283 of 22283 hgu133aCHRLOC found 19059 of 22283 hgu133aCHR found 20584 of 22283 hgu133aENZYME found 2054 of 22283 hgu133aGENENAME found 20650 of 22283 hgu133aGO found 14915 of 22283 hgu133aGRIF found 8341 of 22283 hgu133aLOCUSID found 20755 of 22283 hgu133aMAP found 20481 of 22283 hgu133aPATH found 2826 of 22283 hgu133aPMID found 18665 of 22283 hgu133aSUMFUNC found 1543 of 22283 hgu133aSYMBOL found 20650 of 22283 hgu133aUNIGENE found 20311 of 22283 Mappings found for non-probe based rda files: hgu133aENZYME2PROBE found 577 hgu133aGO2ALLPROBES found 3533 hgu133aGO2PROBE found 2549 hgu133aPATH2PROBE found 121 hgu133aPMID2PROBE found 44683
probe probe • 901 views
ADD COMMENT
0
Entering edit mode
John Zhang ★ 2.9k
@john-zhang-6
Last seen 10.3 years ago
>There appears to be a problem with the Gene Ontology metadata in >hgu133a: > > > library(hgu133a) > > get("GO:0000002", hgu133aGO2ALLPROBES) >[1] "93062_at" "161630_i_at" "96296_at" "100040_at" > > get("93062_at", hgu133aGO) >Error in get(x, envir, mode, inherits) : variable "93062_at" was not >found Yes, it seems that the GO2ALLPROBES environment for hgu133a was corrupted when the data package was built. I assume that the error is limimted as I have checked the hgu95av2, hgu133b, mgu74av2, and rgu34a chips and did not see any repetition. We are in the process of building a new release of all the annotation data packages. The error will be corrected in the new release. Thank you very much for reporting the error.
ADD COMMENT

Login before adding your answer.

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