Re: [Rd] Rd2dvi (PR#9812)

On Thu, 26 Jul 2007 [EMAIL PROTECTED] wrote: > Is this a bug-- > > --- > <234>% R CMD Rd2dvi base.Rd > Converting Rd files to LaTeX ... > base.Rd > Can't use an undefined value as filehandle reference at > /opt/R-2.5.1/lib

[Rd] Rd2dvi (PR#9812)

Is this a bug-- --- <234>% R CMD Rd2dvi base.Rd Converting Rd files to LaTeX ... base.Rd Can't use an undefined value as filehandle reference at /opt/R-2.5.1/lib/R/share/perl/R/Rdconv.pm line 78. ENCS is Creating dvi out

Re: [Rd] sequence(c(2, 0, 3)) produces surprising results, would (PR#9813)

On Thu, 26 Jul 2007 [EMAIL PROTECTED] wrote: > Full_Name: Bill Dunlap > Version: 2.5.0 > OS: Linux > Submission from: (NULL) (70.98.76.47) > > sequence(nvec) is documented to return > the concatenation of seq(nvec[i]), for > i in seq(along=nvec). This produces inconvenient > (for me) results for

Re: [Rd] sequence(c(2, 0, 3)) produces surprising results, would like output length to be sum(input) (PR#9811)

On Thu, 26 Jul 2007 [EMAIL PROTECTED] wrote: > Full_Name: Bill Dunlap > Version: 2.5.0 > OS: Linux > Submission from: (NULL) (70.98.76.47) > > sequence(nvec) is documented to return > the concatenation of seq(nvec[i]), for > i in seq(along=nvec). This produces inconvenient > (for me) results for

[Rd] sequence(c(2, 0, 3)) produces surprising results, would like output length to be sum(input) (PR#9811)

Full_Name: Bill Dunlap Version: 2.5.0 OS: Linux Submission from: (NULL) (70.98.76.47) sequence(nvec) is documented to return the concatenation of seq(nvec[i]), for i in seq(along=nvec). This produces inconvenient (for me) results for 0 inputs. > sequence(c(2,0,3)) # would like 1 2 1 2 3, ign

Re: [Rd] (PR#9810) Problem with careless user of RODBC (was SQL

Your error message was >> d <- sqlFetch(channel, District) > Error in odbcTableExists(channel, sqtable) : >object "District" not found and as you had not defined an object 'District' in that session, it seems perfectly plain. If you want to refer to table "District" you have to give a

Re: [Rd] SQL server service pack 2 prob? (PR#9810)

On Jul 26, 2007, at 9:39 AM, [EMAIL PROTECTED] wrote: > Full_Name: Jeff Lindon > Version: 2.5.0 > OS: mingw32 > Submission from: (NULL) (63.147.8.67) > > > R 2.5.0 seems to be unable to read valid tables from SQL Server > 2005 with > Service Pack 2 installed: > >> version >_ > p

[Rd] SQL server service pack 2 prob? (PR#9810)

Full_Name: Jeff Lindon Version: 2.5.0 OS: mingw32 Submission from: (NULL) (63.147.8.67) R 2.5.0 seems to be unable to read valid tables from SQL Server 2005 with Service Pack 2 installed: > version _ platform i386-pc-mingw32 arch

Re: [Rd] loess prediction algorithm

The loess.demo function in the TeachingDemos package may help you to understand better what is happening (both running the demo and looking at the code). One common reason why predictions from the loess function and hand computed predictions don't match is because the loess function does an additi

Re: [Rd] [R] aggregate.ts

aggregate.tis() in the fame package does what I think is the right thing: > x2 <- tis(1:24, start = c(2000, 11), freq = 12) > y2 <- aggregate(x2, nfreq = 4) > x2 Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec 2000 1 2 2001 3 4 5 6 7 8

[Rd] loess prediction algorithm

Andy, If you could provide an example of the R code with which you call loess(), I can post R code which will duplicate what predict.loess does without having to call the C/Fortran. There are a lot of implementation details that are easy to overlook, but without knowing the arguments to your call

Re: [Rd] loess prediction algorithm

The R interface is just a wrapper for those Netlib C/Fortran functions. I don't think anyone is going to be able (or willing) to read and explain those for you. You do need to understand the loess.control parameters, and I believe they are explained in the White Book. But perhaps you should use