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 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 >> >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 ([EMAIL PROTECTED]). Look for "[ESS] hide function bodies" and "[ESS] outline-minor-mode". Heinz >______________________________________________ >[email protected] 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. > ______________________________________________ [email protected] 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.
