On Wed, 14-Dec-2011 at 09:55AM -0800, Peter Langfelder wrote:
|> On Wed, Dec 14, 2011 at 4:35 AM, Chris Mcowen wrote:
|> > Dear List,
|> >
|> >
|> >
|> > I am unsure if this is the correct list to post to, if it isn't I
apologise.
|> >
|> >
|> >
|> > I am using SSH to access a Linux version of R
On Wed, Dec 14, 2011 at 4:35 AM, Chris Mcowen wrote:
> Dear List,
>
>
>
> I am unsure if this is the correct list to post to, if it isn't I apologise.
>
>
>
> I am using SSH to access a Linux version of R on a remote computer as it
> offers more memory and processing power. The model will take 1-2
What I did in the past (not with R scripts) is to start my jobs using
at (start the job at a specified time e.g. now) or batch (start the
job when the cpu drops below ?%)
at now "R CMD BATCH yourscript.R"
or
batch "R CMD BATCH yourscript.R"
something like that, you'll have to look at the m
On Wed, 14 Dec 2011, Chris Mcowen wrote:
As a Linux newbie, I was wondering if anybody here knew how to keep R
running and interactive and return to it on a later date?
Chris,
Screen will retain the session and keep the process going. Read 'man
screen'.
Whether this works from a remote M
Dear List,
I am unsure if this is the correct list to post to, if it isn't I apologise.
I am using SSH to access a Linux version of R on a remote computer as it
offers more memory and processing power. The model will take 1-2 days to
run, I am accessing R through Putty and when I close the
5 matches
Mail list logo