search for: sdif

...=c(factor="contr.treatment",ordered="contr.poly")) > options(contrasts=c(factor="contr.helmert",ordered="contr.poly")) > options(contrasts=c(factor="contr.sum",ordered="contr.poly")) > library(MASS) # needed for the contrast contr.sdif > options(contrasts=c(factor="contr.sdif",ordered="contr.poly")) The results from anova were igual. For example for the factor Treatment had the same probabilities in every case but SAS treatment helmert sum sdif Pr(>F) 3.073e-05 3.073e-05...

...from SPSS to R/S and am trying to reproduce the results of SPSS in R. I calculated a one-way anova with "spk" as experimental factor and erp as depended variable. The result of the Anova are the same concearning the mean square, F and p values. But I also wanted to caculate the contr.sdif(4) contrast on spk. The results are completely different now. I hope anybody can help me. Thanks, Wolfgang This is what I get in SPSS: Tests of Within-Subjects Contrasts Measure: MEASURE_1 Source SPKType III Sum of Squares df Mean Square F Sig. SPK Level 2 vs. Level 1 3,493 1 3,493 2,026 ,178...

HI there, Consider a data set like this: > x <- data.frame(a=1:10, b=11:20, t=c(1,1,1,2,2,2,3,3,3,3)) > x a b t 1 1 11 1 2 2 12 1 3 3 13 1 4 4 14 2 5 5 15 2 6 6 16 2 7 7 17 3 8 8 18 3 9 9 19 3 10 10 20 3 Here x$t is a vector of integers that represent a moment in time. I would like to calculate a function of a & b at each moment (t0), but using the rows

...vious). Thus the phi's are identified by requiring that they add to zero, and *alpha_l = (phi_2 - phi_l )/2, *alpha_2 = [phi_3 - (phi_l + phi_2)/2] / 3 &c. When the columns of C are not mutually orthogonal the story is not quite so obvious, though. For example take a C matrix using contr.sdif (available in the MASS2 library) > contr.sdif(4) [2-1] [3-2] [4-3] 1 -0.75 -0.5 -0.25 2 0.25 -0.5 -0.25 3 0.25 0.5 -0.25 4 0.25 0.5 0.75 The column sums are all zero so the identification constraint is still the same, but they are not mutually orthogonal. The coefficients do have an easy inter...

...r 'Numerical integration', but glmm output differs. For the intercept e.g. I have a standard error of 0.4354 from glmm and 0.5338 from glmmML. Any idea about this problem?? Thanks in advance Clemens Tilke library (MASS) data (bacteria) contrasts (bacteria$trt) <- structure (contr.sdif (3), dimnames = list (NULL, c ("drug", "enc"))) bacteria.pql <- glmmPQL (y ~ trt + I(week > 2), random = ~ 1 | ID, family = binomial, data = bacteria) summary (bacteria.pql) library (repeated) y1 <- 1 * (bacteria$y == "y") bacteria1 <- data.frame (b...

...k DCS /dev/sdie [2:0:1:161] disk DataCore Virtual Disk DCS - [2:0:1:162] disk DataCore Virtual Disk DCS - [2:0:1:163] disk DataCore Virtual Disk DCS - [2:0:1:164] disk DataCore Virtual Disk DCS - [2:0:1:165] disk DataCore Virtual Disk DCS /dev/sdif [2:0:1:166] disk DataCore Virtual Disk DCS /dev/sdig [2:0:1:167] disk DataCore Virtual Disk DCS /dev/sdih [2:0:1:168] disk DataCore Virtual Disk DCS /dev/sdii [2:0:1:169] disk DataCore Virtual Disk DCS /dev/sdij

As partiter doesn't deallocate itself after finish (anymore), it should be deleted after each loop iteration. diff --git a/com32/chain/chain.c b/com32/chain/chain.c index c08ec6e..f86cd7d 100644 --- a/com32/chain/chain.c +++ b/com32/chain/chain.c @@ -64,27 +64,23 @@ static int is_phys(uint8_t sdifs) static int find_by_sig(uint32_t mbr_sig, struct part_iter **_boot_part) { - struct part_iter *boot_part = NULL; + struct part_iter *iter = NULL; struct disk_info diskinfo; int drive; for (drive = 0x80; drive < 0x80 + fixed_cnt; drive++) { if (disk_get_params(driv...

Dear R-helpers, I have a linear model with a year effect (year is coded as a factor), i.e. the parameter estimates for each level of my year variable have significant P values (see some output below) and I am interested in testing: a) the overall effect of year; b) the significance of each year vis-a-vis every other year (the model output only tests each year against the baseline year). I'd

...tional tests can be handled just by moving variables to the r.h.s. of the linear model specification, but there might be a point in having a more evocative interface, especially where transformed Y's are involved. This could be formula-based or matrix-based: contrasts=ginv(contr.sdif(4)) or formula based: ystruct=~index. -- O__ ---- Peter Dalgaard Blegdamsvej 3 c/ /'_ --- Dept. of Biostatistics 2200 Cph. N (*) \(*) -- University of Copenhagen Denmark Ph: (+45) 35327918 ~~~~~~~~~~ - (p.dalgaard@biostat.ku.dk) FAX: (+45) 3...

For ordered factor the natural contrast coding would be to parametrize by the succsessive differences between levels, which does not assume equal spacing of factor levels as does the polynomial contrasts (implicitly at least). This requires the contr.cum, which could be: contr.cum <- function (n, contrasts = TRUE) { if (is.numeric(n) && length(n) == 1) levs <- 1:n

Dear R-helpers, I try to perform glm's with negative binomial distributed data. So I use the MASS library and the commands: model_1 = glm.nb(response ~ y1 + y2 + ...+ yi, data = data.frame) and predict(model_1, newdata = data.frame) So far, I think everything should be ok. But when I want to perform a glm with a subset of the data, I run into an error message as soon as I want to predict

Hi, I posted the message below last week, but no answers, so I'm giving it another attempt in case somebody who would be able to help might have missed it and it has now dropped off the end of the list of mails. I am fairly new to R and still trying to figure out how it all works, and I have run into a few issues. I apologize in advance if my questions are a bit basic, I'm also no

...t. # nft delete table twst Error: No such file or directory; did you mean table ‘test’ in family ip? delete table twst ^^^^ If you delete a table whose name has been mistyped, error reporting includes a suggestion. * Match on the slave interface through `meta sdif' and `meta sdifname', e.g. ... meta sdifname vrf1 ... * Support for right and left shifts: ... meta mark set meta mark lshift 1 or 0x1 ... This example shows how to shift one bit left the existing packet mark and set the less significant bit to 1. * New -V option...

This small set fixes few bugs, improves gpt handling (under buggy conditions) and implements strict flag with more fine grained control which should fix issues with sanity checks against disk sizes. If this set is allright I'd want to do what I mentioned in older discussion with Ady - backport missing patches from 6.x to 5.x and 4.x so all versions have up to date chain version. Michal