similar to: Cross-platform function availability

I am trying to use winProgressBar, however I find that although setWinProgressBar updates the value on the screen, getWinProgressBar does not return this value. E.g > pb <- winProgressBar() > setWinProgressBar(pb, 0.2) > getWinProgressBar(pb) [1] 0 I tried the same with tkProgressBar, and it is working as I would expect from the documentation. > pb <- tkProgressBar() >

Hi, I tried to add a progress bar to my script, but it seems the "txtProgressBar" function will wipe out what I want to print before it(for example - the "Hello" in following script), and the parameters "title" and "label" do not work either. How can I put a title for the progress bar? or is there any other better function I can use? testit <-

Gracias, Daniel!. No veo claro cómo adaptarlo (en mi caso se trata de un apply de tal modo que para cada item de la lista leo el fichero de datos cuyo nombre se indica, y en total leo tantos ficheros como elementos hay en la lista). Le daré una vuelta a ver si consigo aplicarlo bien y si no en tal caso os consulto. Saluditos! Eva ________________________________ De: daniel

Hi all, I use txtProgressBar to monitor progress of large computations. What I miss is the ability to redirect the progress bar to a stream other than stdout, specifically to the message stream. This would be useful for running Sweave scripts: When redirected to stderr, the bar could be visible even though console output is diverted to the output file (and there would be no cluttering of the

Hola, Carlos: Gracias!. Muy buena idea!. No conocía ese paquete. Se entiende que funciona también en Linuz y Mac, ¿verdad?. Un saludo. Eva ________________________________ De: Carlos Ortega <cof@qualityexcellence.es> CC: daniel <daniel319@gmail.com>; "R-help-es@r-project.org" <R-help-es@r-project.org> Enviado: Miércoles 19 de junio de 2013 22:42 Asunto: Re:

Buenas tardes: ¿Cuál es el modo más adecuado de incorporar una barra de progreso en la ventana de comandos?. Es para acompañar a un proceso de lectura de ficheros de datos... Necesitaba que la solución fuese multiplataforma. Gracias. Un saludo. Eva [[alternative HTML version deleted]]

Hi, I am running R 2.12.0 (windows). example(txtProgressBar) gives me some funny screen output with all kinds of special characters appearing and disappearing. It's happening on two different mashines since vs. 2.12.0. Is this a known issue? Best, Jalla -- View this message in context: http://r.789695.n4.nabble.com/txtProgressBar-strange-behavior-in-R-2-12-0-tp3051976p3051976.html Sent

# Fuente: http://ryouready.wordpress.com/2009/03/16/r-monitor-function-progress-with-a-progress-bar/ library(utils) total <- 20 # create progress bar pb <- txtProgressBar(min = 0, max = total, style = 3) for(i in 1:total){ Sys.sleep(0.1) # update progress bar setTxtProgressBar(pb, i) } close(pb) library(tcltk) total <- 20 # create progress bar pb <- tkProgressBar(title =

Hola Eva, Esta puede ser otra alternativa: http://cran.r-project.org/web/packages/pbapply/pbapply.pdf Saludos, Carlos Ortega www.qualityexcellence.es El 19 de junio de 2013 22:06, Eva Prieto Castro <evapcastro@yahoo.es>escribió: > Gracias, Daniel!. > > No veo claro cómo adaptarlo (en mi caso se trata de un apply de tal modo > que para cada item de la lista leo el fichero de

Hi All, I am trying to build in a progress-tracker into my loops that let me have a sense of their progress. I'd like to be able to output to screen a series of periods "...." etc. for each completion of the loop, but I <don't> want to build a pyramid, e.g. . .. ... .... etc. So I need to be able to delete <the last line> of the console entry to accomplish this.

What's the recommended way to check if an internet connection is available across platforms? I was using is.null(nsl()) but this does not work on windows. Thanks, Hadley

Is there a good strategy for testing examples which should not be run by default? For instance, I have examples which get data from the Internet. If I wrap them in try() then they can be skipped if the Internet is not available, but may not be tested in cases when I would like to know about the failure. (Not to mention that the example syntax is ugly.) If I mark them \dontrun or \donttest

I am reading several hundred files. Anywhere from 50k-400k in size. It appears that when I read these files with R 2.15.1 the process will hang or seg fault on the scan() call. This does not happen on R 2.14.1. This is happening on the precise build of Ubuntu. I have included everything, but the issue appears to be when performing the scan in the method parseTickData. Below is the

Dear R users, I am curious if someone could direct me towards websites/tutorials for uses of progress bars (especially) in R. I can't seem to figure them out. Thanks very much, Scott [[alternative HTML version deleted]]

I have just installed the latest version of R on a openSUSE 12.1 system running on an ORacle VM VirtualBox and have encountered a problem with installing ChemometricsWithR. Here is the output: > library("compiler") > install.packages("ChemometricsWithR") Installing package(s) into ?/home/computation/R/x86_64-unknown-linux-gnu- library/2.15? (as ?lib? is unspecified)

Hi, I am getting the follwoing error while installing gsubfn_0.6-4.tar.gz library for R. R version is 2.15.1 and i am installing on Redhat linux version 2.6.18-238.9.1.el5 (mockbuild at x86-002.build.bos.redhat.com<mailto:mockbuild at x86-002.build.bos.redhat.com>) (gcc version 4.1.2 20080704 (Red Hat 4.1.2-50)) * installing to library ?/home/mapred/installables/R/library? * installing

Hi, source(file,echo=T) will not echo the last comment in "file" if it is the last line in the file. For instance, when sourcing a file containing the following lines #comment 1 a<-1 #comment 2 R will echo > #comment 1 > a<-1 What is the solution to have R echo all of the comment lines? Specific context: This problem arises e.g. in the context of help files (.Rd) whose

Hi again; I have placed many examples in the CTFS Rd pages because my audience really really likes lots of examples in order to understand the options available in a functions. At this time I have set them all to \dontrun{}. however, this isn't because the example command line with its function and options won't work, but rather that CTFS specific datasets must exist to have the

1. I often like to put bits of the output into the manual pages. (We can have a discussion of the value of this elsewhere -- I think it is sometimes a good thing.) In R I need to surround these with \dontrun{} for the sake of the tester, which is fine. But the printed output contains ## Not run and ## End (not run) comments, which defeats the purpose of the lines by breaking them

You've answered my question 2 about why the manual was in odd order > R CMD check was more of a check of the latex version of the files, not > the final manual. I was looking at the result of R CMD check, and it was in random order (perhaps file date?), not just a different collation choice. Very odd. I will cease worrying about what I might have "done wrong". I omitted the