search for: cxy

..., dy), where dx and dy have already been computed for the svd function, but there might be situations where it was less than this, so I guess the safe option would be to include rank = qr(t(x) %*% y)$rank among the outputs. Then the last four lines of the help might be amended to rk <- cxy$rank all.equal(cor(x %*% cxy$xcoef[, 1:rk, drop=FALSE], y %*% cxy$ycoef[, 1:rk, drop=FALSE]), diag(cxy$cor)) all.equal(cor(x %*% cxy$xcoef[, 1:rk, drop=FALSE]), diag(1, rk)) all.equal(cor(y %*% cxy$ycoef[, 1:rk, drop=FALSE]), diag(1, rk)) which I think is more intuitive. Mor...

good morning to the R-help list!, I would like to ask if there is an alternative to the S ploting parameter "cxy" in R. I am trying to port some S code to R that makes use of this "cxy" parameter to scale the graphics, and I don't find this parameter in help(par). thank you, IOsu ------------------------------------------------------------------------------- Jes?s Mar?a Fr?as Celayeta...

Another naive stats question. I'm trying to better understand what boxplots are telling me. I think what I see is the median and the boundaries of the 1st and 3rd quartiles. The whiskers represent the range of the data unless there are points which are outside "range" (default: 1.5) times the distance from the median to that quartile. Is that right? I've read the

Hi all, The C++11 (& C11) compare_exchange functions with explicit memory order allow you to specify two sets of semantics, one for when the exchange actually happens and one for when it fails. Unfortunately, at the moment the LLVM IR "cmpxchg" instruction only has one ordering, which means we get sub-optimal codegen. This probably affects all architectures which use

Is there an equivalent to the S-PLUS par()$cxy in R? Also, is it possible to get notice taken of some equivalent of \n in R when using text()? For what it is worth I am using RW-0.64.1. John Maindonald email : john.maindonald at anu.edu.au Statistical Consulting Unit, phone : (6249)3998 c/o CMA, SMS,...

Howdy! I need to calculate partial correlations and I just can't find out how to do that with R. Can anybody help? Ragnar -.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.- r-help mailing list -- Read http://www.ci.tuwien.ac.at/~hornik/R/R-FAQ.html Send "info", "help", or "[un]subscribe" (in the "body", not the subject !)

...ich I am stuck is that the length of a tick is set by par("tcl") as a fraction of the "height of a line of text". So I would like to draw a line whose length is also this length. However I cannot find out how to convert the into units I can pass into lines(). I thought par("cxy"), but it is too large, as is shown in the code below. Here the red tick marks are longer than the black ones created by axis. I have found the relevant function in plot.c: "GConvertYUnits(Rf_gpptr(dd)->tcl, LINES, NFC, dd);" but can't find the corresponding R function. Can...

Hi, Earlier this year I "upgraded" from wine 20010510 to 20011226 in order to see if some kind of resource leak was fixed which caused screen redraws to get progressively slower and slower and slower and slower, .... That was fixed but there seemed to be a significant number of graphics and UI regressions. I've just upgraded to 20020228 to see if things were any better and within

...warnings: > old.par <- par() > par(old.par) Warning messages: 1: parameter "cin" can't be set in: par(args) 2: parameter "cra" can't be set in: par(args) 3: parameter "csi" can't be set in: par(args) 4: parameter "cxy" can't be set in: par(args) 5: parameter "din" can't be set in: par(args) 6: gamma cannot be modified on this device in: par(args) Is this a mistake or a new feature? If it is a new feature, is there a simple way to avoid the warnings? Thanks, Paul Gilbert

Hello: I am using rpart and would like more background on how the splits are made and how to interpret results - also how to properly use text(.rpart). I have looked through Venables and Ripley and through the rpart help and still have some questions. If there is a source (say, Breiman et al) on decision trees that would clear this all up, please let me know. The questions below pertain to a

I've been using par() to check the graphics parameters associated with both plot(<fitted linear model>) and plot(<grouped data object>). AFAIK the only differences are in the $cxy, $usr, $xaxp, and $yaxp parameters but the background color for the grouped data plot is grey while the linear model plot has a white background. When I've tried par(bg = "white") prior to using the plot(<grouped data object>) command it doesn't seem to make any difference....

Hi, I have two catagorical vectors like this; x = c(1, 2, 4, 2, 1) y = c(2, 4, 2 ,4, 1) I want to set up a barplot with the catagories 1-4 horizontally and number of occurances vertically for each vector x,y. I've tried boxplot(table(x,y), beside=T) and boxplot(c(x,y), beside=T) among others, but can't get it to work...Any ideas? I'd apppreciate any help

...nction(x, y, box.ratio = 1, font = box.dot$font, pch = box.dot$pch, cex = box.dot$cex, col = box.dot$col, outline = T, ...) { ok <- !is.na(x) & !is.na(y) x <- x[ok] y <- y[ok] y.unique <- sort(unique(y)) width <- box.ratio/(1 + box.ratio) w <- width/2 e <- par("cxy")[1] for(Y in y.unique) { X <- x[y == Y] q <- quantile(X, c(0.75, 0.5, 0.25)) iqr <- q[1] - q[3] d <- q[c(1, 3)] + c(1, -1) * 1.5 * iqr up.w <- max(X[X <= d[1]], q[1]) lo.w <- min(X[X >= d[2]], q[3]) outliers <- X[X < lo.w | X > up.w] X <- c...

...gins, legends improperly placed, etc. I checked the default par() settings and found differences between my machine and the server's R instance in 6 parameters. I attempted to set the server-side par() settings to mimic my client machine, but I cannot change the three read-only settings of cra, cxy, and din, and the graphs still look distorted. Is there another way to make the two sets of defaults equal each other? I am using R 2.6.1 on the server and 2.7.0 on my client computer, but I am doubtful that this would have an effect. Any ideas? Thanks! Jason [[alternative HTML version deleted...

what I have: a SuSE 8.0 pro, running samba 2.2.3a as a PDC a deskjet 895 cxi configured in cups cups configured to accept the application/octet-stream mimetype me wanting to upload winXP and win98 drivers to the samba server so that clients just connect, then get the drivers. uploaded drivers from winxp box (bot xp and '98 drivers) directories on samba's PRINT$ ressource got created and

We have a last problem (I hope) before rolling out our new SMB domain using SuSE Linux 8.2 with Samba 2.2.7a and cups 1.1.18. It seams that not every windows printer driver is working correctly. Samba is configured as a PDC and distributes the windows printer driver files. The printing system is cups. Printers are connected via JetDirect-boxes to the network. Printers like the HP LaserJet 4100

...call. However, I am interested in determining values for cex and rot based on the current panel / viewport and device. More specifically, I would like to make adjustments when tick labels overlap on the x-axis, such as labels of a factor. If I use base graphics, par("cin") or par("cxy") or strwidth(), etc. can be used to develop an algorithm to adjust cex or/and rot if needed. I am trying to determine the parameters/settings in grid analogous to par("cin"), etc. mentioned above, knowing that par() has no effect in lattice / grid. I have dug around the sources for...

Hi, I'm newbie with R and don't really know how to add a median line to each of the groups that is not all the plot long. Here is a small working code that i have adapted for my purpose. If somebody could tell me how to draw median lines on each group and not all plot long. ctl <- c(4.17,5.58,5.18,6.11,4.50,4.61,5.17,4.53,5.33,5.14) trt <-

hi, I have a barplot with six clusters of four bars each. Now I would like to add the exact value of each bar as a number above the bar. I hoped to get some tips here. I could simply add text at the different positions, but I don't understand how the margins on the x-axis are calculated (how can I get / calculate the x-ticks of a barplot?). Also I would like to code this flexible enough so

...quot;) and par("ylog") are not Read Only Marc> parameters as listed in the help file and can be set Marc> by the user. Indeed this is confirmed in the comments Marc> in par.r: Marc> #.Pars.readonly <- c("cin","cra","csi","cxy","din") Marc> I noted this today as I was comparing the output of Marc> par() with par(no.readonly = TRUE) and noted that the Marc> latter returns '$xlog' and $ylog' as being Marc> settable. The other 5 par values listed in ?par as Marc&gt...