similar to: pairwise ANOSIM test

Hi all, After my reply on R-Help to the relevant thread, I noted what appear to be a couple of typos in the Details section of ?pairwise.t.test. Note text with '**'. Current text: The **pool.SD** switch calculates a common SD for all groups and **used** that for all comparisons (this can be useful if some groups are small). This method does not actually call t.test, so extra arguments

Hello, I am interested in using ANOSIM (analysis of similarities) which is part of the vegan package. When I look at the programmers notes they mention that "They don't quite trust this method, and someone should study it closely." I was just wondering if this had been done, and whether it had been found reliable or not? Thanks, Kerry Reeves

Un texte encapsul? et encod? dans un jeu de caract?res inconnu a ?t? nettoy?... Nom : non disponible URL : <https://stat.ethz.ch/pipermail/r-help/attachments/20081112/618073fe/attachment.pl>

Hello Everyone,   I've been learning to use R in my spare time over the past several months. I've read about 7-8 books on the subject. Lately I've been testing what I've learned by trying to replicate the analyses from some of my SAS books. This helps me make sure I know how to use R properly and also helps me to understand how the two programs are similar and different.   Below is

An embedded and charset-unspecified text was scrubbed... Name: nem el?rhet? URL: <https://stat.ethz.ch/pipermail/r-help/attachments/20130412/f2e12b77/attachment.pl>

Dear R-help, I have a question about pairwise.t.test and adjustment for multiple comparisons for paired data points. I have the following data: n=c("x", "x", "x", "x", "x", "x", "x", "x", "x", "x", "y", "y", "y", "y", "y", "y",

# I'm doing a pairwise.t.test on a large dataset and need the output in a data frame so I can work further with it, e.g. so I can export it to a spreadsheet. Is there any way to coerce the results to an exportable format? # For example, if I do: test <- pairwise.t.test(numbers, factors, p.adj="bonferroni") # and then write.table(test, file="output.csv",

Dear R Core, pairwise.wilcox.test does not handle "paired = TRUE" correctly; e.g. set.seed(13) x <- rnorm(20) g <- c(rep(1, 10), rep(2, 10)) wilcox.test(x ~ g)$p.value # 0.075 pairwise.wilcox.test(x, g)$p.value # 0.075, o.k wilcox.test(x ~ g, paired = TRUE)$p.value # 0.105 pairwise.wilcox.test(x, g, paired = TRUE)$p.value # 0.075, wrong The line wilcox.test(xi, xj,

Hi list-members can anybody tell me why > pairwise.t.test(val, fac) produces an empty p-table. As shown below: Pairwise comparisons using t tests with pooled SD data: val and fac AS AT Fhh Fm Fmk Fmu GBS Gf HFS Hn jAL Kol R_Fill AT - - - - - - - - - - - - - Fhh - - - - - - - - - - - - - Fm - - - - - - -

Hi R users, My question is, If I have 3 groups, A, B, C and I know mean of A =20, B=21, and C=20.5 and I also know the standard error of A =1.1, B=2.2, C=3.2. Plus, I know A has 30 observations, B has 78, C has 45. But I do not have the raw data. Can I use pairwise.t.test to conduct a Bonferroni test? If yes, Could you give me a hint? Thank you so much Chunhao -- View this message in

Attached file I use to test GPT code. I used qemu 1.2 with seabios with LSI enabled and a patch diff --git a/src/blockcmd.c b/src/blockcmd.c index 77c690f..df4fb1e 100644 --- a/src/blockcmd.c +++ b/src/blockcmd.c @@ -146,7 +146,7 @@ scsi_init_drive(struct drive_s *drive, const char *s, int prio) // We do not bother with READ CAPACITY(16) because BIOS does not support // 64-bit LBA

Hi, how can I extract the t-values after running a pairwise.t.test? The output just list the p-values. Many thanks for your help. Cheers Guido ____________________________________ Guido J. Parra School of Tropical Environment Studies and Geography James Cook University Townsville Queensland 4811 Phone: 61 7 47815824 Fax: 61 7 47814020 Mobile: 0437630843 e-mail:

Dear all, I am perplexed when trying to get the same results using pairwise.t.test and t.test. I'm using examples in the ISwR library, >attach(red.cell.folate) I can get the same result for pairwise.t.test and t.test when I set the variances to be non-equal, but not when they are assumed to be equal. Can anyone explain the differences, or what I'm doing wrong? Here's an example

Dear all, I am looking for an equivalent of the pairwise.t.test() function using a complex survey design. Any suggestions on this or how to account for weights using the pairwise.t.test itself? Thanks, V [[alternative HTML version deleted]]

What's the difference between t.test(x, y) and pairwise.t.test()? Is it just that the former takes two vectors, whereas the latter takes a vector and a factor?

Hi again Timo, As agreed earlier tonight, you'll find as attachments 4 diffs (diff -u) implementing the new workaround "tb-lsub-flags". The 4 impacted files are: ./src/imap/imap-settings.h ./src/imap/imap-settings.c ./src/imap/cmd-list.c ./src/config/all-settings.c Here is the proposed description for the dovecot.conf file: # tb-lsub-flags: # Usually IMAP servers don't

Hi there, I am trying to do multiple pairwise Wilcoxon signed rank tests in a manner similar to: a <- c(runif(1000, min=1,max=50), rnorm(1000, 50), rnorm(1000, 49.9, 0.5), rgeom(1000, 0.5)) b <- c(rep("group_a", 1000), rep("group_b", 1000), rep("group_c", 1000), rep("group_d", 1000)) pairwise.wilcox.test(a, b, alternative="two.sided",

Hi, If I set the p.adjust="none", does it meant that the output p values from the pairwise.t.test will be the same as those from individual t.tests (set var.equal=T, alternative="t")? I actually got different p values from the two tests. See below. Is it supposed to be this way? Thanks Johnny > x [1] 61.6 52.7 61.3 65.2 62.8 63.7 64.8 58.7 44.9 57.0 64.3 55.1 50.0 41.0

i use openbsd/i386, dovecot-cvs(today), mysql-5.0.18 today, i change the mysql_dbuser_password form OLD_PASSWORD to PASSWORD then dovecot can't connect to mysql-server shell$> mysql -u root -p mysql$> SET PASSWORD FOR 'db_user'@'localhost' = PASSWORD('db_pw'); now, dovecot CAN NOT connect to mysql-server shell$> mysql -u root -p mysql$> SET PASSWORD FOR

I'd like to put forward the following patch for dovecot-sieve. Essentially this just merges in some changes made in CMU sieve 2.3.8 and as such brings the behaviour more in line with RFC 3834 "Recommendations for Automatic Responses to Electronic Mail": - fixes erroneous sender "-request" substring match - checks for existence of a selection of list-* headers -