2010/9/20 Aditya Mahajan
On Mon, 20 Sep 2010, Johan Sandblom wrote:
Why are you using input output redirection
R .... < \Rfile\space > \Rfile.out
rather than a simple
R .... \Rfile\space \Rfile.out
Originally, I think it was because it was the only way that worked on both Windows and Linux, but lately it is because R CMD BATCH produces produces a couple of lines of processing times at the end, which I do not want.
@Hans, mtxrun be completely silent when used to launch external programs and only give some output if --verbose is passed.
That would make more sense.
BTW, there is a serious bug in the R module: each code chunck carries a state with it (--save --restore), but this state can depend on which chunck was changed.
Indeed. But I have learned to live with it.
This "bug" can be avoided by doing some book keeping for the external state (saving the file to a different name and restoring it), or by not using --save and --restore.
Yes. But the book keeping gets a little complicated and ugly since it needs to be done from within R (--save takes no arguments). Or possibly all chunks after an altered chunk should be run. Thanks for your comments, Johan
Aditya ___________________________________________________________________________________ If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://tex.aanhet.net archive : http://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___________________________________________________________________________________
-- Johan Sandblom, MD PhD m +46735521477 Sweden "What is wanted is not the will to believe, but the will to find out, which is the exact opposite" - Bertrand Russell