Dear Rainer
On Wed, Apr 25, 2012 at 5:34 PM, Rainer Schuermann
wrote:
> <>=
>
I like the 'eval=FALSE' trick.
> SweaveInput( "setup.Rnw" )
>
> and from here, I can suse the named chunks almost like function calls, as you
> you describe below. The advantage (for me) is that I have only one place
What I usually do when I have to write a report with some functions I use
multiple times is that I put them in a separate file (call it "setup.Rnw" or
so).
The first chunk there loads the libraries, sets initial variable values etc:
<>=
library( xtable )
d <- iris
ind <- 1
@
Then I have a num
On 25/04/2012 10:20 AM, Liviu Andronic wrote:
On Wed, Apr 25, 2012 at 3:41 PM, Duncan Murdoch
wrote:
> I would use the last method, or if the calls were truly repetitive (i.e.
> always identical, not just the same pattern), use a named chunk.
>
Labeled chunks are indeed what I was looking for
On Wed, Apr 25, 2012 at 3:41 PM, Duncan Murdoch
wrote:
> I would use the last method, or if the calls were truly repetitive (i.e.
> always identical, not just the same pattern), use a named chunk.
>
Labeled chunks are indeed what I was looking for [1]. As far as I
understand, this is what "Sweave
On 12-04-25 7:41 AM, Liviu Andronic wrote:
Dear all
When using Sweave, I'm always hitting the same bump: I want to group
repetitive calls in a function, but I want both the results and the
function calls in the printed output. Let me explain myself.
Consider the following computation in an Sweav
Dear all
When using Sweave, I'm always hitting the same bump: I want to group
repetitive calls in a function, but I want both the results and the
function calls in the printed output. Let me explain myself.
Consider the following computation in an Sweave document:
summary(iris[,1:2])
cor(iris[,1:2
6 matches
Mail list logo
