[knitr] Child documents: Input child files into the main document | /knitr/demo/child/

Guest *jamiefolson* @ 2012-05-15 18:04:42 originally posted:

Is it intentional that child .tex documents are always created in the base directory even if they're in subdirectories?

Guest *Jared* @ 2012-05-30 02:58:53 originally posted:

Loving knitr for everything from making a book, to an article to a presentation.  I'm trying to be more sophisticated about child documents (right now I wrote a function that checks all listed child documents and only knits them if the Rnw files have changed, then use include{} to pull them into the master Rnw file).

I'm trying out <<child-sec,child='folder file.rnw',eval="TRUE">>= but I have two questions/problems.

First, when each file is in a different, non-nested, folder only the first one works because the working directory has been changed.  The comment by Jamie makes it seem like the Rnw files can be stored in different directorys but I can't make it work.

Second, when using the above command, does it only compile the Rnw to tex when the Rnw has been changed, or does it compile every time?  That can be a big cost saving.

Thank you for the amazing work and any answers you can provide.

Guest *Martin* @ 2012-06-07 12:20:57 originally posted:

I was wondering if there is a way to include child documents when using Markdown instead of LaTeX?
Thanks for a great tool! 

访客 *Rapheal210* @ 2012-06-13 05:40:40 写道：

谢兄，你好。关于“Knit child documents in a standalone mode”部分，我有点没看明白。到底set_parent函数应该放在什么位置？是放在child doucument里面么？
比如把child document写成下面的样子：<<set-parent, echo="FALSE," cache="FALSE">>=
set_parent('knitr-input.Rnw')
@
<<test-child, out.width="2in">>=
1+1
rnorm(5)
plot(1)
boxplot(1:10)
str(mtcars)@ 是这样么？但是这样好像child document还是无法单独编译啊？还是我的理解有误？
 

Guest *Rafik Margaryan* @ 2012-10-18 11:07:51 originally posted:

Dear Yihui Xie
I have created one Rproject multiple Rnw files under different subdirectories. 
for knit-ing I use knit("subdir1/ex1.Rnw","subdir1/ex1.tex"). 
I would like to compile ex1.tex in its directory(subdirectory of main project). 
Compiling with Rstudio compilePDF gives me error of not finding figures which I also put under subdir1/fig . 
How I should manage this multiple Rnw files within R (preferably). 
Many thanks

Guest *hugo koopmans* @ 2012-11-13 14:52:10 originally posted:

Hello Yihui Xie,

First a big thank you for your great work!

Intro: I would like to create an automated data quality report builder in R + knitr. Using R Studio at the moment and I have played around with it all. The point is that I would like to read in an arbitrary dataset and then for each variable do some analysis in R plus some tex stuff describing the field, missing values may be a histogram plot ect ect. So if the variable is nummeric I wuld like to plot a histogram also some text on outliers and missing values . If the variable is a factor I would like to do something completly different. But in thee end I would like to knit a pdf docuemnt that holds high level overview plus for each variable a section or chapter in the pdf. I am puzzle how to generate rnw file for each variable...

My question: Can I use knitr (child documents?) to generate a document page for each variable in a dataset?

option: Is there a way to template rnw files so I can give a certain R variable to it?

hugo

Guest *Henrik Nyhus* @ 2013-01-28 07:54:24 originally posted:

Hi Yihui, thanks for this great package!

I'm having some trouble weaving a child

<<titlepage, child="titlepage.Rnw" ,="" eval="TRUE">>=
@

containing utf-8 encoded letters (norwegian - ÆØÅ) with the "Complie PDF" function in Rstudio.

The outputs .tex (and .pdf) files read for instance "" instead of "ø".

When I add all the text from the child direct into the main .Rnw file, it compiles normally. Using the command "knit" it also typesets the .tex file properly, which I then externally can compile to a .pdf, which probably would imply that the problem lies on Rstudio rather than knitr.
BTW: The "Compile PDF"-funciton in Rstudio puts all "childs" in ONE .tex/ file, where as "knit"/"knit2pdf creates a .tex for each .Rnw.

All files and preambles for the utf-8 encoding is regarded.

Being new to compiling LaTex in Rstudio, I am not sure whether it's due to user, R(studio) or knitr error.

I could not find any information on anyone experiencing the same issues, and thought it would be interesting for you to know about it.
Perhaps something you already have heard of?

Beste Regards,
Henrik

ps! There ist some additional code appering after posting this that obviously is not containes in the "original" .Rnw file.

Guest *Paul* @ 2013-02-07 11:52:41 originally posted:

This is all good and dandy but it doesn't work with AucTeX in Emacs. RefTeX knows about commands like include and input and follows them to build a comprehensive table of contents nor navigation. I tried to create a workaround with

newcommand{kinclude}[1]{
Sexpr{knit_child("#1")}
}

and then add a child with

kinclude{introduction.Rnw}

This doesn't work, though. I get the following error:

Error in auto_out_name(input) : cannot determine the output filename automatically introduction.Rnw

Guest *onichi* @ 2013-02-07 16:17:30 originally posted:

Thanks for knitr, Yihui!

Is there anyway to do selective prints if a document is detected to be the parent as opposed to a file? I have some children files I would like to be able to structure as separate documents, with their own pre-ambles, etc. and then be able to compile them into full documents.

However, if they are included as a child, it will use whatever the parent document has.

Thank you!

Guest *Petri Koistinen* @ 2013-03-06 10:24:47 originally posted:

I am in the process of converting a largish LaTeX document so that it uses knitr. I am having trouble with child documents, which I definitely want to include{}, not input{} in the master file. If my master file master.rnw looks something like this:

<<>>=
opts_knit$set(child.command = 'include')
@

<<child=c('intro.rnw', 'other.rnw')="">>=
@

and I run knit(), then I will get the file master.tex, which looks like this

include{intro.tex}

include{other.tex}

This creates havoc when I run LaTeX. The correct format for include{} is to omit the .tex externsion, like this:

include{intro}

include{other}

Is there an easy fix to this problem?

Thank you!

Guest *Roman Ahmed* @ 2013-07-24 00:42:20 originally posted:

Hi Yihui,

Thanks for developing this awesome package .... love it.

I have a question regrading child document specially it's evaluation and storing results.

I want to use child documents as the sections of an article. My problem is computing time for few sections are very long (few days). Therefore I want to make sure once the parent document is evaluated the results for the child document is stored there and when I texify the same parent document next time with an additional section (child) it doesn't evaluate the codes for the previously evaluated child but prints the results.

Definitely I am assuming independence between sections/childs in terms of computing.

Is there any way to do that? Cheers, Roman

Guest *Doihanh* @ 2013-10-01 23:06:08 originally posted:

Hi Yihui, I am compiling a big document containing several child documents. One question: How can I include references for each chapter which are child documents? What I got now is all chapters have the same list of references. Thanks, Doi.

Guest *ADPowers* @ 2013-11-02 22:40:20 originally posted:

Yihui, I have a large document (100+ pages) which is 99.99% plain LaTeX, however, I want to include maybe one or two knitr Chunks. What is the best way to do this, without converting every file to .Rnw and knitting as per usual.