Hi all, Most of the analyses I do are short little once-and-done type things that are easily encapsulated in a .Rnw file. However, I sometimes end up with projects that take an extended amount of time. Usually these projects are not easily encapsulated in an .Rnw file, so I have been using a single .R file with lots of comments. The problem with this approach is keeping track of what you have done and what the results were. Once the .R file gets to be a certain size, the comments aren't as useful, and I find it easy to get lost. I have to assume that others have encountered this problem and hopefully have come up with something more elegant. Any suggestions? Best, Jim -- James W. MacDonald, M.S. Biostatistician Affymetrix and cDNA Microarray Core University of Michigan Cancer Center 1500 E. Medical Center Drive 7410 CCGC Ann Arbor MI 48109 734-647-5623 ********************************************************** Electronic Mail is not secure, may not be read every day, and should not be used for urgent or sensitive issues.
James MacDonald <jmacdon <at> med.umich.edu> writes:> > Hi all, > > Most of the analyses I do are short little once-and-done type things that areeasily encapsulated in a .Rnw> file. However, I sometimes end up with projects that take an extended amountof time. Usually these> projects are not easily encapsulated in an .Rnw file, so I have been using asingle .R file with lots of comments.> > The problem with this approach is keeping track of what you have done andwhat the results were. Once the .R> file gets to be a certain size, the comments aren't as useful, and I find iteasy to get lost. I have to assume> that others have encountered this problem and hopefully have come up withsomething more elegant.> > Any suggestions? > > Best, > > Jim >One possible choice is the intuitively structured approach of "Projects" in Tinn-R (see http://www.sciviews.org/Tinn-R/). -- D L McArthur <dmca <at> ucla.edu>
At 22:36 23.07.2007 +0000, D L McArthur wrote:>James MacDonald <jmacdon <at> med.umich.edu> writes: > >> >> Hi all, >> >> Most of the analyses I do are short little once-and-done type thingsthat are>easily encapsulated in a .Rnw >> file. However, I sometimes end up with projects that take an extendedamount>of time. Usually these >> projects are not easily encapsulated in an .Rnw file, so I have beenusing a>single .R file with lots of comments. >> >> The problem with this approach is keeping track of what you have done and >what the results were. Once the .R >> file gets to be a certain size, the comments aren't as useful, and Ifind it>easy to get lost. I have to assume >> that others have encountered this problem and hopefully have come up with >something more elegant. >> >> Any suggestions? >> >> Best, >> >> Jim >> >One possible choice is the intuitively structured approach of "Projects" in >Tinn-R (see http://www.sciviews.org/Tinn-R/). > -- D L McArthur <dmca <at> ucla.edu> >Or, in case you use emacs and ESS you could find some hints at the ESS help list (ess-help at stat.math.ethz.ch). Look for "[ESS] hide function bodies" and "[ESS] outline-minor-mode". Heinz>______________________________________________ >R-help at stat.math.ethz.ch 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. >