search for: rep3

...ot;,3),rep("post",3)),6)), + subj = factor(rep(paste("subj",1:6,sep=""),c(6,6,6,6,6,6))), + Group = factor(c(rep("Treat",18),rep("Control",18)))) > rt.df rt rep prepost subj Group 1 287 rep1 pre subj1 Treat 2 283 rep2 pre subj1 Treat 3 261 rep3 pre subj1 Treat 4 298 rep1 post subj1 Treat 5 302 rep2 post subj1 Treat 6 280 rep3 post subj1 Treat 7 211 rep1 pre subj2 Treat 8 272 rep2 pre subj2 Treat 9 222 rep3 pre subj2 Treat 10 285 rep1 post subj2 Treat 11 253 rep2 post subj2 Treat 12 252 rep3 post subj2 Treat 13 266 rep1 pre subj3...

Hi, R 2.5.0 isn't auto-completing paths properly as it used to. E.g. suppose I have: > dir("CEL/choe") [1] "chipC-rep1.CEL" "chipC-rep2.CEL" "chipC-rep3.CEL" "chipS-rep1.CEL" [5] "chipS-rep2.CEL" "chipS-rep3.CEL" Now if I do: ReadAffy("CEL/choe/ch<tab> # => ReadAffy("CEL/choe/chip ReadAffy("CEL/choe/chipC<tab> # => ReadAffy("CEL/choe/chipC-rep ReadAffy("CEL/choe/chipC-r...

...uot; (see below) is how my original data are arranged, and I know that with melt() I can reshape it like "y" (see below). However, I just want to build a matrix like the "y" matrix, but with only 2 dimensions. Something like this: year Site specie Pres Rep1 Rep2 Rep3 Rep4 Rep5 1 2003 2021 MICH 1 0 0 1 1 0 3 2003 2021 MISA 1 1 0 0 0 0 4 2003 2021 MOBO 1 1 1 0 0 0 where "year" and "specie" are not another dimen...

...e sitting on each brick in plain view and picking a split-brain winner is now WAY more complicated. You would have to re-assemble things. We were quite good and fixing broken Gluster 3.4 nodes, but we are *much* happier with the Arbiter node and sharding. It is a huge difference. We could go to Rep3 but we like the extra speed and we are comfortable with the Arb limitations (we also have excellent off cluster backups <grin>). > Also, on a two-node setup it is *guaranteed* for updates to one node > to put offline the whole volume? If you still have quorum turned on, then yes....

...cursive=TRUE) #extractModelParameters reads all the output files from the Test folder and create the following variables in R for each file read: #C..PilotStudy.Mplus_Input.Test.rep1.out.unstandardized.est #C..PilotStudy.Mplus_Input.Test.rep2.out.unstandardized.est #C..PilotStudy.Mplus_Input.Test.rep3.out.unstandardized.est modelResultsTemp <- as.data.frame(modelResults) MeansTempC1 = rep(NA ,9) counter = 1 for (f in 1:3) { i=31 for (g in 1:3) { OutputFileName <- paste("modelResultsTemp$C..PilotStudy.Mplus_Input.Test.rep",f,".out.unstandardized.est[",i,"]&quot...

...ch a situation? How can I "decide" which (reconstructed) file is the one to keep rather than to delete? > > We were quite good and fixing broken Gluster 3.4 nodes, but we are > *much* happier with the Arbiter node and sharding. It is a huge > difference. > We could go to Rep3 but we like the extra speed and we are comfortable > with the Arb limitations (we also have excellent off cluster backups > <grin>). > > >> Also, on a two-node setup it is *guaranteed* for updates to one node >> to put offline the whole volume? > > If you sti...

Il 25-08-2017 08:32 Gionatan Danti ha scritto: > Hi all, > any other advice from who use (or do not use) Gluster as a replicated > VM backend? > > Thanks. Sorry, I was not seeing messages because I was not subscribed on the list; I read it from the web. So it seems that Pavel and WK have vastly different experience with Gluster. Any plausible cause for that difference? > WK

Il 23-08-2017 18:51 Gionatan Danti ha scritto: > Il 23-08-2017 18:14 Pavel Szalbot ha scritto: >> Hi, after many VM crashes during upgrades of Gluster, losing network >> connectivity on one node etc. I would advise running replica 2 with >> arbiter. > > Hi Pavel, this is bad news :( > So, in your case at least, Gluster was not stable? Something as simple > as an

...    -0.008224680  0.0175580130 > TRATP       -0.007558013  0.0182246797 > TRATR       -0.011558013  0.0142246797 > TRATT       -0.008224680  0.0175580130 > CORTEC2     -0.065010796 -0.0481320614 > CORTEC3     -0.175010796 -0.1581320614 > REP2        -0.022323748 -0.0005333952 > REP3        -0.019466605  0.0023237476 > REP4        -0.025180890 -0.0033905381 > REP5        -0.023276129 -0.0014857762 >   > He puesto 0,85 porque me piden una significación del 0.15% > Ya me diréis. >  Un saludo. > Juan Bautista Relloso Barrio > Coordinador de Equipos e Infrae...

> On Apr 23, 2018, at 10:49 AM, WK <wkmail at bneit.com> wrote: > > From some old May 2017 email. I asked the following: > "From the docs, I see you can identify the shards by the GFID > # getfattr -d -m. -e hex path_to_file > # ls /bricks/*/.shard -lh | grep GFID > > Is there a gluster tool/script that will recreate the file? > > or can you just sort

...: 467: # All the bricks delare finished 468: 469: # Replicate part 470: volume rep1 471: type cluster/replicate 472: subvolumes cbrick1 cbrick4 cbrick7 473: end-volume 474: 475: volume rep2 476: type cluster/replicate 477: subvolumes cbrick5 cbrick8 cbrick14 478: end-volume 479: 480: volume rep3 481: type cluster/replicate 482: subvolumes cbrick9 cbrick15 cbrick18 483: end-volume 484: 485: volume rep4 486: type cluster/replicate 487: subvolumes cbrick13 cbrick16 cbrick19 488: end-volume 489: 490: volume rep5 491: type cluster/replicate 492: subvolumes cbrick17 cbrick20 cbrick23 493...