?stop explains why this happens and how to change it.
You can also set options(error=expression(NULL)) to ignore all errors, and
use tryCatch() (or its wrapper try()) skip particular expressions if tjhey
fail.
But surely in your example your script should check for existence of the
file by fi
There is a "try" function that you can wrap around functions.
Hope this helps!
Sincerely,
Erin
On 6/12/08, Josh <[EMAIL PROTECTED]> wrote:
> I'm invoking R in batch mode from a bash script as follows:
>
> R --no-restore --no-save --vanilla
> <$TARGET/$directory/o2sat-$VERSION.R>
> $TARGET/$dire
I'm invoking R in batch mode from a bash script as follows:
R --no-restore --no-save --vanilla
<$TARGET/$directory/o2sat-$VERSION.R>
$TARGET/$directory/o2sat-$VERSION.Routput
When R comes across some error in the script however it seems to halt
instead of running subsequent lines in the script:
3 matches
Mail list logo