On Sat, May 17, 2008 at 8:18 AM, Jeremiah Rounds
<[EMAIL PROTECTED]> wrote:
>
>
>
> Someone mentioned Sweave. Sweaves value really depends on who you are and
> what your doing. Its work cycle is not appropriate for students or anyone
> that needs rapid cycle prototyping imo. Its great flaw is that it does not
> work well with "changing a little something--looking at the results in R"
> followed by "changing a little something in latex--looking at the results in
> dvi" repeated over and over and over again. The reason is it has to repeat
> far to much work in each cycle. Often times repeating long calculations.
Or you could wrap the time-consuming parts in:
if(exists("whatever", where=1)) { do timeconsuming thing}
as long as you are sure that if the results are already there they
don't need to be recalculated.
You can get caught by not having something recalculated that you
expect to be new, but if
you have lengthy calculations (in my case a couple of days for some
things) it is very useful.
Sarah
--
Sarah Goslee
http://www.functionaldiversity.org
______________________________________________
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.
