similar to: length 1 offset in glm

Hi, I have run into another problem using offsets, this time with the predict function, where there seems to be a contradiction again between the behavior and the help page. On the man page for predict.lm, it says Offsets specified by offset in the fit by lm will not be included in predictions, whereas those specified by an offset term in the formula will be. While it indicates nothings about

Hi, I'm raising the issue, again, of those pesky thin lines that show up with a pdf graphics device, otherwise known as FAQ 7.36. I have read the FAQ and understand that I can eliminate them by adjusting the anti-aliasing option for viewing them on the screen, but this doesn't necessarily eliminate them for a print device or for transferring them into a powerpoint or similar type of

Peter Thank you for the information. I accidentally deleted Ken's post without having read it. Ken' s thought is great but as you said awful to implement I thought that capture.output would come in handy some time when I first saw it on an unrelated reply. Just thought :- the latex listings package may have alternatives If I remember correctly it has wrapping and other goodies but I

We announce the release of package MPDiR version 0.1-11 which contains data sets and functions to support the forthcoming book "Modeling Psychophysical Data in R" by K. Knoblauch and L. T. Maloney, Use R! Vol 32, Springer (expected publication date: September 2012). The package includes several data sets from published psychophysical experiments using detection and rating scale measures

I've started to use the parallel package and it works very well speeding things up. Thank you for making this easy to do. Should I have expected that parCapply would return a vector when parApply returns a matrix? library(parallel) x <- matrix(rnorm(8), nc = 2) apply(x, 2, function(y) y) [,1] [,2] [1,] -0.9649685 0.91339851 [2,] -1.4313140 0.13457671 [3,] 1.0499248

This is to announce a new package MLCM on CRAN. The package provides functions for estimating perceptual scales by maximum likelihood from data collected in a conjoint measurement experiment. Data for conjoint measurement are typically collected using a psychophysical procedure. The stimuli vary along 2 or more dimensions. The observer views pairs of stimuli and judges which stimulus of each pair

This is to announce a new package MLCM on CRAN. The package provides functions for estimating perceptual scales by maximum likelihood from data collected in a conjoint measurement experiment. Data for conjoint measurement are typically collected using a psychophysical procedure. The stimuli vary along 2 or more dimensions. The observer views pairs of stimuli and judges which stimulus of each pair

Hi, I'm getting an error that I don't understand when updating an nls object. Here is a toy example. dd <- structure(list(Contrast = c(0.00376, 0.03759, 0.12782, 0.25564, 0.50376, 1), Response = c(0.29915, 6.13248, 29.01709, 30.0641, 29.46581, 27.67094)), .Names = c("Contrast", "Response"), class = "data.frame", row.names = c(NA, -6L)) m1 <-

Hi, In the Sweave output for summary for several types of model objects and also for the comparison of models with anova, I find that that the display of the call(s) or formula does not obey the width option, even with keep.source=TRUE set, so that a long formula will overshoot the margins in the document. I would like to know if there is a good way to correct that. Looking at the print.summary

I'm having a problem with dotted lines (lty = 3) in the pdf output in documents generated with Sweave. In the displayed pdf, the dotted line does not show up and in the printed output, it is there but does not seem to respect the lwd argument, for example, it is very faint despite using lwd = 3. The dotted line is correct in a quartz window and if I save the Quartz window to a pdf and

This post about length 1 offsets on R help seems to have been ignored (sorry deleted original email - is there a way to continue thread in this case?) https://stat.ethz.ch/pipermail/r-help/2009-February/189352.html It does seem to be a bug, in that glm does not behave as documented. In fact the same bug applies to lm as well. I don't think the suggested fix works though - Y isn't

Must packages in the Depends field of the DESCRIPTION file have NAMESPACES? I haven't seen this explicitly indicated anywhere. I am writing a small package and find that when I add the abind package to the list of the Depends field, I get an error in R CMD check of the build. * checking package name space information ... OK * checking package dependencies ... ERROR Packages required but not

Hi, I'm trying to redefine the contrasts for a linear model. With a 2 level factor, x, with levels A and B, a two level factor outputs A and B - A from an lm fit, say lm(y ~ x). I would like to set the contrasts so that the coefficients output are -0.5 (A + B) and B - A, but I can't get the sign correct for the first coefficient (Intercept). Here is a toy example, set.seed(12161952) y

Hi, I would have thought that these two constructions would produce the same result but they do not. Resp <- rbinom(10, 1, 0.5) Stim <- rep(0:1, 5) mm <- model.matrix(~ Stim) Xb <- mm %*% c(0, 1) ifelse(Resp, log(pnorm(Xb)), log(1 - pnorm(Xb))) pnorm(as.vector(Xb), lower.tail = Resp, log.p = TRUE) > ifelse(Resp, log(pnorm(Xb)), log(1 - pnorm(Xb))) [1] -0.6931472 -1.8410216

New packages psyphy and MLDS are available on CRAN: psyphy ncludes an assortment of functions useful in analyzing data from pyschophysical experiments. It includes functions for calculating d' from several different experimental designs, links for mafc to be used with the binomial family in glm (and possibly other contexts) and selfStart functions for estimating gamma values

New packages psyphy and MLDS are available on CRAN: psyphy ncludes an assortment of functions useful in analyzing data from pyschophysical experiments. It includes functions for calculating d' from several different experimental designs, links for mafc to be used with the binomial family in glm (and possibly other contexts) and selfStart functions for estimating gamma values

On Sat, Jan 28, 2023 at 2:49 PM Kenneth Knoblauch <ken.knoblauch at inserm.fr> wrote: > > Hi, > > I'm struggling to find if there is a simple way to make the lines and points overlap in a legend for a lattice plot using auto.key. Here is a toy example of what doesn't work (for me) as the lines and points are adjacent rather than overlapping: > > library(lattice)

I'm having a problem with the mfg option of par. Am I making an error in my usage? Here is a simple example that I thought would plot to the 4 corners of a 2x2 plot but doesn't plot to the lower right and plots twice on the upper left. par(mfrow = c(2, 2)) pos <- as.matrix(expand.grid(1:2, 1:2)) for (ix in 4:1) { par(mfg = pos[ix, ]) plot(1:5) } Thank you in advance. R version

I'm using scan in a script to record a series of responses of the user as a function of some graphs that I put up on the screen. A toy version would be, y <- rep(NA, 3) for (ix in seq( length(y) ) ) { y[ix] <- scan( n = 1 ) } However, if I include any code after this loop, for example, y <- rep(NA, 3) for (ix in seq( length(y) ) ) { y[ix] <- scan( n = 1 ) } y I get an error

Hi, When I compile the construction \begin{Scode}{eval=FALSE} ?HSP \end{Scode} with Sweave and latex, it outputs in the pdf as, > `?` (HSP) which is not incorrect but a bit more formal than I wanted for demonstrating the use of the help shortcut. I would like the output to look like, > ?HSP but I can't seem to make this work. I have also tried the results=verbatim argument.