Jim Holtman wrote: > > One of the things that you should do is to use Rprof > to see where time is being spent. > Rprof is great! I didn't know such functionality existed.
But I am a very destructive user; I think I found a way to break Rprof: if I do f <- my.slow.function then call f(...) Rprof will report that f (and not my.slow.function) was called <evil grin>. I noticed that because I "tested" Rprof with one of my programs that do test cases; these test cases run with an array of functions, by calling each function from the array - precisely what can't be traced by Rprof :-) Alberto Monteiro ______________________________________________ R-help@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-help PLEASE do read the posting guide http://www.R-project.org/posting-guide.html and provide commented, minimal, self-contained, reproducible code.
