Per document or per machine sounds good to me. BTW, I have created a
ticket online so this issue will not be forgotten:
http://www.lyx.org/trac/ticket/8032
Regards,
Yihui
--
Yihui Xie
Phone: 515-294-2465 Web: http://yihui.name
Department of Statistics, Iowa State University
2215 Snedecor Hall, Am
Le 03/02/2012 04:08, Jack Tanner a écrit :
Jean-Marc Lasgouttes lyx.org> writes:
It is probably doable to set the timeout value per converter. This would
be the best solution IMO.
I can be convinced that setting the timeout value on a chunk-by-chunk basis is
excessive, but per converter is
Jean-Marc Lasgouttes lyx.org> writes:
>
> It is probably doable to set the timeout value per converter. This would
> be the best solution IMO.
I can be convinced that setting the timeout value on a chunk-by-chunk basis is
excessive, but per converter is too coarse. Maybe per document?
Le 01/02/12 22:18, Yihui Xie a écrit :
Hi,
I guess LyX should give the literate programming modules (e.g.
Sweave/knitr) more time to run their code. Currently I see the time
allowed is about 3 minutes, and LyX will raise an error after that. I
tested it with the following chunk in Sweave:
It i
Yihui Xie yihui.name> writes:
>
> The time-out restriction is from LyX, so Sweave/knitr cannot do
> anything about it.
You're right; what I meant to say was that I'd want to tell LyX to allow longer
Sweave/knitr runs for particular chunks.
The time-out restriction is from LyX, so Sweave/knitr cannot do
anything about it.
My current workaround is to export Rnw from LyX, run knitr on it with
cache turned on, and run LyX again since the time-consuming chunks
have been calculated and cached.
Regards,
Yihui
--
Yihui Xie
Phone: 515-294-
Liviu Andronic gmail.com> writes:
>
> Can the 'timeout' be configured? Or is it possible to treat
> Sweave/knitr documents differently? Regards
One Sweave/knitr computation is different from another. I'd expect 1+1 to be
computed quickly, but I also have some simulations that take hours, and I'
On Wed, Feb 1, 2012 at 10:18 PM, Yihui Xie wrote:
> I guess LyX should give the literate programming modules (e.g.
> Sweave/knitr) more time to run their code. Currently I see the time
> allowed is about 3 minutes, and LyX will raise an error after that. I
>
I've been bitten by this in the past, a
Hi,
I guess LyX should give the literate programming modules (e.g.
Sweave/knitr) more time to run their code. Currently I see the time
allowed is about 3 minutes, and LyX will raise an error after that. I
tested it with the following chunk in Sweave:
<<>>=
for (i in 1:100) {
Sys.sleep(10)
