R help - Nov 2012 - Puzzling "Execution halted"

I wrote an R program that does heavy computations with hundreds of
lines of code. It's running fine both interactively and in batch mode
on a Mac OS X computer. The program also has no problem running on a
Linux system (Fedora 14) interactively. However, when I try it on the
terminal in batch mode on the Linux system, it chokes in the middle of
the computation with the "Execution halted" error message.

I already put try or tryCatch in those places where computation may
throw an error. And the warnings are set in default (options(warn=1)).
I wish I could provide the code for help, but that seems impractical.
How to debug this?

Thanks,
Gang

Le mardi 20 novembre 2012 ? 12:54 -0500, Gang Chen a ?crit
:
> I wrote an R program that does heavy computations with hundreds of
> lines of code. It's running fine both interactively and in batch mode
> on a Mac OS X computer. The program also has no problem running on a
> Linux system (Fedora 14) interactively. However, when I try it on the
> terminal in batch mode on the Linux system, it chokes in the middle of
> the computation with the "Execution halted" error message.
> 
> I already put try or tryCatch in those places where computation may
> throw an error. And the warnings are set in default (options(warn=1)).
> I wish I could provide the code for help, but that seems impractical.
> How to debug this?
Have a look at your /var/log/messages: it might well be the
out-of-memory killer killing your R process because it eats too much
RAM...

My two cents

On 20/11/2012 12:54 PM, Gang Chen wrote:
> I wrote an R program that does heavy computations with hundreds of
> lines of code. It's running fine both interactively and in batch mode
> on a Mac OS X computer. The program also has no problem running on a
> Linux system (Fedora 14) interactively. However, when I try it on the
> terminal in batch mode on the Linux system, it chokes in the middle of
> the computation with the "Execution halted" error message.
>
> I already put try or tryCatch in those places where computation may
> throw an error. And the warnings are set in default (options(warn=1)).
> I wish I could provide the code for help, but that seems impractical.
> How to debug this?
I think you have to use the old-fashioned way:  sprinkle print() or 
cat() statements through your program to identify where the error is 
happening.

Duncan Murdoch