Hi, Sometimes I want to "reset" the R interpreter (as if I quit and started it again, with everything starting from scratch). The main reason for this is when I expreriment with calculations, and later form them into general functions, sometimes I forget to include variables or reset some settings which I don't notice because they are already set. This causes problems during batch calculations, and a lot of wasted time. Currently I am using rm(list=ls()), but it only cleans up the namespace. Quitting and restarting is slow. What I am looking for is a function that resets the R interpreter without restarting it. I did search the archives, but maybe I am using the wrong keywords: reset gives me a lot of results. I would appreciate any advice on this, ie if there is no function to do this, how people cope with this problem. Thanks, Tamas -- Tam??s K. Papp E-mail: tpapp at axelero.hu Please try to send only (latin-2) plain text, not HTML or other garbage.
If you haven't tried 1.9.0 yet it does start up faster than 1.8.1. Tamas Papp <tpapp <at> axelero.hu> writes: : : Hi, : : Sometimes I want to "reset" the R interpreter (as if I quit and : started it again, with everything starting from scratch). The main : reason for this is when I expreriment with calculations, and later : form them into general functions, sometimes I forget to include : variables or reset some settings which I don't notice because they are : already set. This causes problems during batch calculations, and a : lot of wasted time. : : Currently I am using rm(list=ls()), but it only cleans up the : namespace. Quitting and restarting is slow. What I am looking for is : a function that resets the R interpreter without restarting it. : : I did search the archives, but maybe I am using the wrong keywords: : reset gives me a lot of results. I would appreciate any advice on : this, ie if there is no function to do this, how people cope with this : problem. : : Thanks, : : Tamas :
Gabor Grothendieck <ggrothendieck at myway.com> wrote:
If you haven't tried 1.9.0 yet it does start up faster than 1.8.1.
For what it's worth, on my SunBlade 100,
R 1.7.1 started in 4 seconds of CPU time, 25 seconds of wall-clock time
R 1.9.0 starts in 3 seconds of CPU time, 20 seconds of wall-clock time.
I measured the time by doing
% time R
> quit("no")
It's really good to see *any* improvement in startup time, and I must
thank the R developers for even *trying* to do anything about it. There's
some way to go yet; octave starts in under a second.