Joel
2009-Jun-10 21:16 UTC
[R] Preventing .Call from printing a blank line to the R console on Windows
Hello everyone, I am using the CVODES integrator in the Rsundials package. Every time I call the integrator, a blank line is printed in the console. Using debug, I was able to isolate the problem to this line in the function cvodes(...): solutions = .Call("cvodes", PACKAGE = "Rsundials", as.double(y), ... Since I am running the integrator thousands of times, I wind up with thousands of blank lines. This makes it hard to print out periodic updates from a for loop; they are lost among all the blank lines! Is it somehow possible to stop this .Call command from printing a blank line? Thank you for your help.
Duncan Murdoch
2009-Jun-10 23:04 UTC
[R] Preventing .Call from printing a blank line to the R console on Windows
On 10/06/2009 5:16 PM, Joel wrote:> Hello everyone, > > I am using the CVODES integrator in the Rsundials package. Every time > I call the integrator, a blank line is printed in the console. Using > debug, I was able to isolate the problem to this line in the function > cvodes(...): > > solutions = .Call("cvodes", PACKAGE = "Rsundials", as.double(y), ... > > Since I am running the integrator thousands of times, I wind up with > thousands of blank lines. This makes it hard to print out periodic > updates from a for loop; they are lost among all the blank lines! > > Is it somehow possible to stop this .Call command from printing a > blank line?The best way is to fix the package so it doesn't do that, but a workaround using capture.output() or sink() is probably possible. Duncan Murdoch
Reasonably Related Threads
- try() with silent=TRUE not preventing printing of error message
- Blank console and no boot
- Blank console but X11 works on MCP79 - old regression since 3.8
- Blank console but X11 works on MCP79 - old regression since 3.8
- Blank console but X11 works on MCP79 - old regression since 3.8