similar to: make check and postscript output in R 1.7.1

This looks like a bug? Unable to use scan(pipe()) while profiling. I have no idea whether this version of R violates the "do not use `Rprof' in an executable built for profiling" warning in ?Rprof. Thanks -Don > version _ platform powerpc-apple-darwin1.4 arch powerpc os darwin1.4 system powerpc, darwin1.4 status Patched major 1 minor 3.1 year

Don MacQueen <macq@llnl.gov> writes: > When I run the example in R 1.6.2, and view it with gs, I get a good plot. > When I run the example in R 1.7.0, and view it with gs, I get a bad plot. > (run on the same host) > > My "bad plot" is as described by Stephen. ... > (followed by ~200000 lines of the same type, with slowly changing values) > > In the

Hi, I do have it installed on 2 Macs as well (OS X 10.2.8 and 10.3.7) and what I need does work, however if you do the command check routine some problems will likely be revealed. At least there were problems for me. Denis Le 08 févr. 2005, à 12:23, r-help-request@stat.math.ethz.ch a écrit : > De: Don MacQueen <macq@llnl.gov> > Date: 07 février 2005 16:05:14 GMT+01:00 > À:

I am wondering if there is a CRAN package that includes a utility function that will "rotate" file names, in the same sense that operating systems sometimes rotate log files. Or maybe there's something in base R. That is, we have a set of file names, say file1, file2, file3, and when the function is called, file3 is deleted, file2 is renamed file3, file1 is renamed file2, and

> From: Don MacQueen [mailto:macq at llnl.gov] > > At 5:29 PM +0100 4/30/03, Luke Whitaker wrote: > > > >At the risk of starting a religous war, isn't java the obvious choice > >for a platform independent GUI ? I know java suffered a lot from > >early over hypeing when it wasn't really ready, but in the last year > >or two I've seen some very

Hi Don, wow, you are so right. I picked that piece up from the bloggers tutorial and since I am R naive yet, I thought it was all one step moving_average = forecast(ma(tdat[1:31], order=2), h=5) Truly, I usually print and check at every step I can, as painful as it is sometimes. Great lesson for this novice usR. So the first and last values are NA in each case? Do you know why? Should I replace

Begin forwarded message: > From: Dan Kelley <Dan.Kelley at Dal.Ca> > Date: March 19, 2004 12:00:01 PM AST > To: Don MacQueen <macq at llnl.gov> > Subject: Re: [R] osx/fink: cannot do "R INSTALL" (library mixup) > > That works perfectly! THanks. I did > 524 export PKG_LIBS="-L/usr/local/lib -L/sw/lib" > 525 R INSTALL pspline > and

I have encountered a problem with merge() that appears to be a bug. Here's an example to illustrate it. > tmp1 <- data.frame(a=letters[1:3],b=LETTERS[2:4],x=1:3) > tmpa <- expand.grid(a=letters[1:4],b=LETTERS[1:4]) > tmpm.1 <- merge(tmpa,tmp1) > tmpm.2 <- merge(tmp1,tmpa) Error in "names<-.default"(*tmp*, value = vnames) : names attribute must

You are right that there are no NAs in the practice data. But there are NAs in the moving average data. To see this, break your work into two separate steps, like this: tnr.ma <- ma(dat3[1:28], order=3) TNR_moving_average <- forecast(tnr.ma, h=8) I think you will find that the warning comes from the second step. Print tnr.ma and you will see some NAs. -Don -- Don MacQueen Lawrence

I have found that data imported from SAS using read.xport() in package foreign (installed recently) does not match the original data, when the data consists of character strings that are only one character long. Here is an example. ---- SAS commands to create the data ---- options nocenter; data foo; a='a'; b='bb'; length c d $2; c='c'; d='

I have an XML file that has within it the coordinates of some polygons that I would like to extract and use in R. The polygons are nested rather deeply. For example, I found by trial and error that I can extract the coordinates of one of them using functions from the XML package: doc <- xmlInternalTreeParse('doc.kml') docroot <- xmlRoot(doc) pgon <-

It's not unusual for R users (like me!) to think they've found a bug, when in fact it's their own error. I would like to ask, however, about the situation where a user has studied the situation enough to be very confident they've found a bug. In that case, what procedure would the R core team like users to follow: 1) post to r-help, then wait for a confirmation and request

I'm trying to figure out how to get out of this situation: > source('monit.r') Error in file(file, "r") : All connections are in use > showConnections() description class mode text isopen can read can write > help.search('connection') Error in file(file, "r") : All connections are in use > q() Save workspace image? [y/n/c]: y Error

This is not a bug, and has nothing to do with times. For example: > round(1.03,1) [1] 1 Formatting is not the same as rounding. Perhaps you are assuming R formats numbers according to the concept of significant digits, but it doesn't. See the help page for the format function to get started with understanding R's rules for formatting numbers when it displays them. Maybe also some

Thank you for both replies Don & Rui, The very issue here is that there is a search that needs to be done within a text field and I agree with Rui later comment that regexpr might indeed be the time consuming piece of code. I might try to optimise this piece of code later on, but for the time being I am working on the following part of building a neural network to try indeed classifying some

Hello Don, thank you for your response. I appreciate your help. I am using the forecast package, originally I found it following a forecasting example on bloggers.com https://www.r-bloggers.com/time-series-analysis-using-r-forecast-package/ And subsequently located the complete pdf https://cran.r-project.org/web/packages/forecast/forecast.pdf Since I created this practice data using the

Thanks Don and Jim, "Get" did the trick! That command is new to me, and is exactly what this problem needed. The syntax that worked is actually slightly simpler than what was suggested. This is what worked: all.comps <- ls(pattern="^res") for(i in all.comps){ obj = get(i); ... Thanks again. --Kelly V. -----Original Message----- From: MacQueen, Don [mailto:macqueen1 at

Hi Dan, Hi All, I read the below post. I am wondering how do I know which "keys" are available, e.g. "core.r" and "pre". Where kind I find the definition of what can be adjusted and which "words" to use? Kind regards Georg > Gesendet: Donnerstag, 08. Juni 2017 um 16:16 Uhr > Von: "Nordlund, Dan (DSHS/RDA)" <NordlDJ at

Thanks it worked for me. I wanted to plot days since planting on x-axis 1 and years on x-axis 3. LAI_simulation$Date <- as.Date( LAI_simulation$Date, '%Y/%m/%d') LAI_simulation$Date <- as.integer(LAI_simulation$Date - as.Date("2009-10-07")) plot(LAI~Date,data=LAI_simulation,xlab="Days since Oct, 7,

I have a failure in 'make check' and I would appreciate assistance regarding what to do about it. Thanks -Don Installing R-1.2.3 on build[99]% uname -sr SunOS 5.8 (for those who may recall my previous request for help, I have updated GCC to 2.95.3, and configured with gcc, GCC's c++, and f77 [not g77]) Running 'make check' got this: creating `no-segfault.R'