GO.db/GOSim bugged or my bad?
1
0
Entering edit mode
lejeczek ▴ 10
@lejeczek-7688
Last seen 4.7 years ago
United Kingdom

hi everybody,

I'm trying something seemingly simple but it segfaults and I wonder it this might be a bug?

I run:

"

library(GOSim)
library(org.Hs.eg.db)
library(org.Mm.eg.db)
library(GO.db)
setEvidenceLevel(evidences = "all", organism=org.Hs.egORGANISM, gomap=org.Hs.egGO)
calc.diffusion.kernel(method="diffKernelLLE", m=5, normalization.method="sqrt", DIR="/tmp")

"

and it fails:

"

initializing GOSim package ...
-> retrieving GO information for all available genes for organism 'human' in GO database
-> filtering GO terms according to evidence levels 'all'
-> loading files with information content for corresponding GO category (human)
finished.
-> retrieving GO information for all available genes for organism 'Homo sapiens' in GO database
-> filtering GO terms according to evidence levels 'all'
calculating diffusion kernel 'diffKernelLLE' for ontology BP using evidence codes 'all' (Homo sapiens) ...
Note: method with signature ‘Matrix#matrix’ chosen for function ‘-’,
 target signature ‘ddiMatrix#matrix’.
 "ddiMatrix#ANY" would also be valid

 *** caught segfault ***
address 0x7ffefe409dc8, cause 'memory not mapped'

Traceback:
 1: E %*% K %*% E
 2: E %*% K %*% E
 3: calc.diffusion.kernel(method = "diffKernelLLE", m = 5, normalization.method = "sqrt",     DIR = "/tmp")


"

Could this be a bug?

many thanks

 

 

 

go.db software error bug • 1.4k views
ADD COMMENT
0
Entering edit mode
@herve-pages-1542
Last seen 16 hours ago
Seattle, WA, United States

Hi peljasz,

When misused, software is expected to either (from best to worse): (a) raise an error, (b) raise a warning, or (c) silently return a wrong result. But not to crash. So yes, clearly a bug. I tried to reproduce this but the call to calc.diffusion.kernel() is still running after 10 minutes...

No answer from the maintainer of GOSim so far. Maybe it would have helped if you had included the gosim tag to your post as it was suggested to you when you filled the Post Form. Anyway, you might have better luck trying to contact the maintainer directly:

> maintainer("GOSim")
[1] "Holger Froehlich <frohlich@bit.uni-bonn.de>"

Don't forget to provide the output of your sessionInfo() (call it right before you call the command causing the crash i.e. calc.diffusion.kernel in your case).

H.

ADD COMMENT

Login before adding your answer.

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