Rscript is very handy. But I'd like to specify output paths at runtime, e.g.: my.Rscript input > output
.
message()
is great for logging to STDERR, but Rscript seems to systematically output WARNING: ignoring environment value of R_HOME
to STDOUT, even if specifying --vanilla
or --no-environ
.
Any workarounds?
(thi开发者_Python百科s is R scripting front-end version 2.13.0 (2011-04-13))
i assume this is very old. but, with bash, etc.:
unset R_HOME
before running Rscript should do the trick. and, with csh, etc.:
unsetenv R_HOME
should likewise work. since the R front-end script sets R_HOME (after complaining), i don't see any reason for leaving R_HOME set. (possibly i'm missing something.)
If you know which R call in the script is generating the warning, suppressWarnings()
can be used to wrap the expression generating the warning. That is certainly in the "workaround" camp.
精彩评论