At 6:44 AM +0100 7/30/05, Prof Brian Ripley wrote:
>This depends on what else is going on. My guess is that you are
>running the Aqua GUI, and it is servicing the GUI which is taking
>the time, not R itself.
Actually, no, I am not using the Aqua GUI. Not even a "framework" build:
../source
This depends on what else is going on. My guess is that you are running
the Aqua GUI, and it is servicing the GUI which is taking the time, not R
itself.
On all of Linux, Solaris and Windows (RGui or Rterm) Sys.sleep() does use
very close to zero resources at the beginning of a session, but th
Don MacQueen wrote:
> I done something very similar -- have R watch a file, and whenever
> new data is added to the file, read the new data from the file. In my
> case, new data was arriving once per minute, so I needed to have R
> wait about a minute before looking for new data.
>
> On my unix
I done something very similar -- have R watch a file, and whenever
new data is added to the file, read the new data from the file. In my
case, new data was arriving once per minute, so I needed to have R
wait about a minute before looking for new data.
On my unix-based system, I found that if I
Tae-Hoon Chung
> Sent: Friday, July 29, 2005 12:13 PM
> To: RHelp
> Subject: [R] Way to make R idle for some time and try
> something again later
>
> Hi, All;
>
> I have a question. In R, what is the best way to make R idle
> for a while and
> try something again lat
Which operating system are you using ?
See help(Sys.sleep), which might be what you want but there may be other
ways in determining if a file is being accessed by another program.
Regards, Adai
On Fri, 2005-07-29 at 12:13 -0700, Tae-Hoon Chung wrote:
> Hi, All;
>
> I have a question. In R, wh
On 7/29/2005 3:13 PM, Tae-Hoon Chung wrote:
> Hi, All;
>
> I have a question. In R, what is the best way to make R idle for a while and
> try something again later? For example, suppose there is an R job which
> accesses a file that may be shared with other active jobs. So when the file
> is being
Hi, All;
I have a question. In R, what is the best way to make R idle for a while and
try something again later? For example, suppose there is an R job which
accesses a file that may be shared with other active jobs. So when the file
is being accessed by other job, your job will not be able to acc