Add this to your startup so that all errors are caught and the
statement and calling stack are printed out. This aids a lot in
debugging, especially when using scripts:
options(error=utils::recover)
On Mon, Apr 13, 2009 at 3:09 PM, SHANE MILLER, BLOOMBERG/ 731 LEXIN
smille...@bloomberg.net
Try
source(...whatever..., echo = TRUE, max = )
On Mon, Apr 13, 2009 at 3:09 PM, SHANE MILLER, BLOOMBERG/ 731 LEXIN
smille...@bloomberg.net wrote:
source(C:\\Documents and Settings\\smiller53\\Desktop\\perf.r)
Error in eval.with.vis(expr, envir, enclos) : element 1 is empty;
the part
source(C:\\Documents and Settings\\smiller53\\Desktop\\perf.r)
Error in eval.with.vis(expr, envir, enclos) : element 1 is empty;
the part of the args list of 'c' being evaluated was:
perf.r is a long script. how can I determine which line the error occurred on?
TIA, SHane
3 matches
Mail list logo