similar to: PBX / Asterisk integration

I don't think it has much to do with transform in particular: > BOD <- data.frame(Time = 1:6, demand = runif(6)) > BOD[["X"]] <- BOD[1:2] * seq(6); BOD Time demand X.Time X.demand 1 1 0.8649628 1 0.8649628 2 2 0.5895380 4 1.1790761 3 3 0.6854635 9 2.0563906 4 4 0.4255801 16 1.7023206 5 5 0.5738793 25 2.8693967 6 6 0.9996713

I think you meant to call BOD[,1] From ?transform, the ... arguments are supposed to be vectors, and BOD[1] is still a data.frame (with one column). So I don't think it's surprising transform gets confused by which name to use (X, or Time?), and kind of compromises on the name "Time". It's also in a note in ?transform: "If some of the values are not vectors of the

The idea is that one wants to write the line of code below in a general way which works the same whether you specify ix as one column or multiple columns but the naming entirely changes when you do this and BOD[, 1] and transform(BOD, X=..., Y=...) or other hard coding solutions still require writing multiple cases. ix <- 1:2 transform(BOD, X = BOD[ix] * seq(6)) On Tue, Jul 24, 2018 at

Is this not supposed to work? > dput(BOD, file = "/BOD.R") > source("/BOD.R") Error in attributes(.Data) <- c(attributes(.Data), attrib) : row names must be 'character' or 'integer', not 'double' > dput(iris, file = "/iris.R") > source("/iris.R") Error in attributes(.Data) <- c(attributes(.Data), attrib) :

I ran a function called BoxCox, taken from the book by Venables and Ripley, for checking the need for power transformation. This function works fine using the version 0.50 of R, but gives an error message with version 0.60. The lm function in version 0.60 is different from that in version 0.50. Is there a bug in the new lm function? Kung-Sik Chan >

Note the inconsistency in the names in these two examples. X.Time in the first case and Time.1 in the second case. > transform(BOD, X = BOD[1:2] * seq(6)) Time demand X.Time X.demand 1 1 8.3 1 8.3 2 2 10.3 4 20.6 3 3 19.0 9 57.0 4 4 16.0 16 64.0 5 5 15.6 25 78.0 6 7 19.8 42 118.8 >

Hi All, I'm trying to run nls on the data from the study by Marske (Biochemical Oxygen Demand Interpretation Using Sum of Squares Surface. M.S. thesis, University of Wisconsin, Madison, 1967) and was reported in Bates and Watts (1988). Data is as follows, (stored as mydata) time bod 1 1 0.47 2 2 0.74 3 3 1.17 4 4 1.42 5 5 1.60 6 7 1.84 7 9 2.19 8 11 2.17 I then

I am just starting to code in R and need some help as I am used to doing this in SAS. I have a dataset that looks like this: Chemical Well1 Well2 Well3 Well4 BOD 13.2 14.2 15.5 14.2 O2 7.8 2.6 3.5 2.4 TURB 10.2 14.6 18.5 17.3 and so on with more chemicals.... I would like to transpose my data so that it looks like this: Chemical WellID Value BOD Well1 13.2 BOD Well2 14.2 BOD Well3 15.5 BOD

On 2/17/23 19:34, Liam R. Howlett wrote: > * Danilo Krummrich <dakr at redhat.com> [230217 08:44]: >> Split up the MA_STATE() macro such that components using the maple tree >> can easily inherit from struct ma_state and build custom tree walk >> macros to hide their internals from users. >> >> Example: >> >> struct sample_iter { >> struct

Hello, When I do: dbWriteTable(con, "r.BOD", cbind(row_names = rownames(BOD), BOD)) ...can I specify the data types such as varchar(12), float, double precision, etc. for each of the fields/columns? If not, what is the best way to create a table with specified field data types (with the RpgSQL package/R)? Regards, Ben [[alternative HTML version deleted]]

Hello, I'm wondering if it is possible to ring X number of extensions simultaneously, and each answered call can be handled with some code. I can do a huntgroup-esque way of dialling, but I want all the dialled numbers to be picked up. I hope this makes sense.. If not please say.. Many thanks! Andy -------------- next part -------------- An HTML attachment was scrubbed... URL:

Full_Name: Madeleine Yeh Version: 1.9.1 OS: AIX 5.2 Submission from: (NULL) (151.121.225.1) After compiling R-1.9.1 on AIX 5.2 using the IBM cc compiler, I ran the checks. One of them failed. Here is the output from running the check solo. root@svweb:/fsapps/test/build/R/1.9.1/R-1.9.1/tests/Examples: ># ../../bin/R --vanilla < stats-Ex.R R : Copyright 2004, The R

On 2/28/23 17:24, Liam R. Howlett wrote: > * Danilo Krummrich <dakr at redhat.com> [230227 21:17]: >> On Tue, Feb 21, 2023 at 01:20:50PM -0500, Liam R. Howlett wrote: >>> * Danilo Krummrich <dakr at redhat.com> [230217 08:45]: >>>> Add infrastructure to keep track of GPU virtual address (VA) mappings >>>> with a decicated VA space manager

I have about 5 incoming USA SIP lines, but my provider does not have any sort of roll-over or huntgroup feature. Does anybody have an idea on how I can create a general number that will ring to the next available, non-busy SIP line that I have? Is there a provider out there that would do this? Any suggestions would be greatly welcome. Thank you. -------------- next part --------------

require(ppls) data(BOD) X<-BOD[,1] y<-BOD[,2] Xtest=seq(min(X),max(X),length=200) dummy<-X2s(X,Xtest,deg=3,nknot=20) Z<-dummy$Z Ztest<-dummy$Ztest size<-dummy$sizeZ P<-Penalty.matrix(size,order=2) lambda<-200 number.comp<-3 penalized.pls(Z,y,P=lambda*P,ncomp=number.comp)$coefficients # By default kernel=F

Sorry, couldn't resist... From: Gabor Grothendieck > > ov$vn1 is not a variable. It is the result of applying the $ > function to the ov and vn1 arguments. ... which would suggest: get("$")(get("ov"), "vn1"). 8-) Andy > For example, using BOD which is a data frame that comes with > R, rather than get("BOD$Time") use

Hello, I'm using package RpgSQL. Is there a better way to create a multi-line query/character string? I'm looking for less to type and readability. This is not very readable for large queries: s <- 'create table r.BOD("id" int primary key,"name" varchar(12))' I write a lot of code, so I'm looking to type less than this, but it is more readable from

A new version of sqldf, version 0.2-0, has been uploaded to CRAN and should be available on most mirrors by now. NEW - works with the new version of DBI package, DBI 0.2-5. The default action of this version of DBI quotes those column names in select statements that are SQL reserved words (rather than appending __1 to them which was the previous default action). As a result it should no

A new version of sqldf, version 0.2-0, has been uploaded to CRAN and should be available on most mirrors by now. NEW - works with the new version of DBI package, DBI 0.2-5. The default action of this version of DBI quotes those column names in select statements that are SQL reserved words (rather than appending __1 to them which was the previous default action). As a result it should no

Dear list, I have encountered a problem with predict.nls (Windows XP, R.2.5.0), but I am not sure if it is a bug... On the nls man page, an example is: DNase1 <- subset(DNase, Run == 1) fm2DNase1 <- nls(density ~ 1/(1 + exp((xmid - log(conc))/scal)), data = DNase1, start = list(xmid = 0, scal = 1)) alg = "plinear", trace =