@GuangchuangYu , @huerqiang
At the Bioconductor support forum an issue/error was reported regarding the function buildGOmap: https://support.bioconductor.org/p/9156358/
I had a quick look at it, and it seems this is because a) the required input for buildGOmap seems to be counter-intuitive, and b) buildGOmap explicitly expects as input a column labelled "GO".
Regarding a):
The required input for buildGOmap (1st column should be the geneids, 2nd column the GOIDs) seems to be counter-intuitive because for the generic enrichment functions enricher and GSEA the reverse order is rather required for the input TERM2GENE (thus 1st column the GOIDs, and 2nd column the geneids)...
Maybe good to align this, or at least explain it better at the help page? Also add an example on the help page?
Regarding b):
The function buildGOmap_internal has hard-coded the requirement that the column with the GOIDs should be labelled GO:
|
res <- setNames(anc[y$GO], y[,1]) |> |
and
|
names(res) <- c(names(y)[1], "GO") |
This requirement is not stated at the help page of buildGOmap, so could you please add that? It now results in the reported error.
Thanks,
G
FWIW: I have attached the GO mapping file that was used on the Bioconductor support forum, and thus gave issues. It was downloaded from https://www.pseudomonas.com/goterms/list (as csv).
gene_ontology_csv.csv
@GuangchuangYu , @huerqiang
At the Bioconductor support forum an issue/error was reported regarding the function
buildGOmap: https://support.bioconductor.org/p/9156358/I had a quick look at it, and it seems this is because a) the required input for
buildGOmapseems to be counter-intuitive, and b)buildGOmapexplicitly expects as input a column labelled "GO".Regarding a):
The required input for
buildGOmap(1st column should be the geneids, 2nd column the GOIDs) seems to be counter-intuitive because for the generic enrichment functionsenricherandGSEAthe reverse order is rather required for the inputTERM2GENE(thus 1st column the GOIDs, and 2nd column the geneids)...Maybe good to align this, or at least explain it better at the help page? Also add an example on the help page?
Regarding b):
The function
buildGOmap_internalhas hard-coded the requirement that the column with the GOIDs should be labelledGO:GOSemSim/R/buildGOmap.R
Line 41 in 1800f40
and
GOSemSim/R/buildGOmap.R
Line 45 in 1800f40
This requirement is not stated at the help page of
buildGOmap, so could you please add that? It now results in the reported error.Thanks,
G
FWIW: I have attached the GO mapping file that was used on the Bioconductor support forum, and thus gave issues. It was downloaded from https://www.pseudomonas.com/goterms/list (as
csv).gene_ontology_csv.csv