search for: x66

With the storage array in place it's now trivial to support CLOCK_TAI in the vdso. Instead of extending the array to accomodate CLOCK_TAI, make use of the fact that: - CLOCK ids are set in stone - CLOCK_THREAD_CPUTIME is never going to be supported in the VDSO so the array slot 3 is unused - CLOCK_TAI is id 11 which results in 3 when masked with 0x3 Add the mask to the basetime array

On Fri, 14 Sep 2018, Andy Lutomirski wrote: > > On Sep 14, 2018, at 5:50 AM, Thomas Gleixner <tglx at linutronix.de> wrote: > > > > With the storage array in place it's now trivial to support CLOCK_TAI in > > the vdso. Instead of extending the array to accomodate CLOCK_TAI, make use > > of the fact that: > > > > - CLOCK ids are set in stone

> On Sep 14, 2018, at 7:27 AM, Thomas Gleixner <tglx at linutronix.de> wrote: > > On Fri, 14 Sep 2018, Andy Lutomirski wrote: >>> On Sep 14, 2018, at 5:50 AM, Thomas Gleixner <tglx at linutronix.de> wrote: >>> >>> With the storage array in place it's now trivial to support CLOCK_TAI in >>> the vdso. Instead of extending the array to

> On Sep 14, 2018, at 5:50 AM, Thomas Gleixner <tglx at linutronix.de> wrote: > > With the storage array in place it's now trivial to support CLOCK_TAI in > the vdso. Instead of extending the array to accomodate CLOCK_TAI, make use > of the fact that: > > - CLOCK ids are set in stone > - CLOCK_THREAD_CPUTIME is never going to be supported in the VDSO so >

> On Sep 14, 2018, at 5:50 AM, Thomas Gleixner <tglx at linutronix.de> wrote: > > With the storage array in place it's now trivial to support CLOCK_TAI in > the vdso. Instead of extending the array to accomodate CLOCK_TAI, make use > of the fact that: > > - CLOCK ids are set in stone > - CLOCK_THREAD_CPUTIME is never going to be supported in the VDSO so >

...straight away and they've appeared as 'hda' and 'hdc'. I've managed to partition hdc (hda was already setup) and format it - this was VERY slow and 'top' showed a significant amount of interrupt time. A bit of Googling found the right command to enable DMA (hdparm -X66 -d1 /dev/hda etc.) and this seems to have cured that problem! While Googling I found a LOT of info on the SIL controller and Linux but it was all for various kernels and linux versions - can anyone steer me in the right direction for info on this setup with RHEL3/Centos - specifically: 1) Should...

...x16 + x17 + x18 + x19 + x20 + x21 + x22 + x23 + x24 + x25 + x26 + x27 + x28 + x29 + x30 + x31 + x32 + x33 + x34 + x35 + x36 + x37 + x38 + x39 + x40 + x41 + x42 + x43 + x44 + x45 + x46 + x47 + x48 + x49 + x50 + x51 + x52 + x53 + x54 + x55 + x56 + x57 + x58 + x59 + x60 + x61 + x62 + x63 + x64 + x65 + x66 + x67 + x68 + x69 + x70 + x71 + x72 + x73 + x74 + x75 + x76 + x77 + x78 + x79 + x80) it gives me an error "Error in eval(expr, envir, enclos) : object 'x3' not found" which I dont know why I am given those errors. The other thing is that when I use the "glm.fit", I can g...

...quot;,"X48","X49","X50","X51","X52","X53","X54","X55","X56","X57","X58","X59","X60","X61","X62","X63","X64","X65","X66","X67","X68","X69","X70","X71","X72","X73","X74","X75","X76","X77","X78","X79","X80","X81","X82","X83","X84",&quot...

...5,X26,X40,X41,X77) Guilda3<-cbind(X22,X28,X69) Guilda4<-cbind(X29,X30,X31,X32,X33,X34,X35,X36,X37,X78) Guilda5<-cbind(X3,X8,X18,X23,X63,X82,X83) Guilda6<-cbind(X6,X38,X39,X44,X45,X46,X47,X49,X50,X51,X52,X53,X54,X55,X56,X57,X58,X59,X60,X61,X62,X84) Guilda7<-cbind(X1,X2,X42,X43,X64,X65,X66,X67,X68,X79,X80) Guilda8<-cbind(X7,X15,X16,X70,X71,X72,X73,X74,X75,X76) Guilda9<-cbind(X4,X9,X10,X11,X12,X13,X14,X81) Resul.Guilda1<-sum(apply(Guilda1,2,sum)) Resul.Guilda2<-sum(apply(Guilda2,2,sum)) Resul.Guilda3<-sum(apply(Guilda3,2,sum)) Resul.Guilda4<-sum(apply(Guilda4,2,sum))...

...X48","X49","X50","X51" > ,"X52","X53","X54","X55","X56","X57","X58","X59","X60","X61" > ,"X62","X63","X64","X65","X66","X67","X68","X69","X70","X71" > ,"X72","X73","X74","X75","X76","X77","X78","X79","X80","X81" > ,"X82","X83","X84...

..."X49" "X50" "X51" "X52" "X53" "X54" "X55" "X56" "X57" "X58" "X59" "X60" [61] "X61" "X62" "X63" "X64" "X65" "X66" "X67" "X68" "X69" "X70" "X71" "X72" "X73" "X74" "X75" "X76" "X77" "X78" "X79" "X80" [81] "X81" "X82" "X83"...

Hello, I have looked on https://www.r-project.org/bugs.html , but it seems that this is the only way to do it. The issue is that the precision used by write.csv is on consistant for big files. See the following code: First I create a large dataframe filled with random uniform values. Then I write it to .csv and print out the first and last lines. df = data.frame(replicate(100, runif(1000000,

...e the conditions are categoricals. model <- lm(X2 +X3+X4+X5+X6+X7+X8+X9+X10+X11+X12+X13+X14+X15+X16+X17+X18+X19+X20+X21+X22+X23+X24+X25+X26+X27+X28+X29+X30+X31+X32+X33+X34+X35+X36+X37+X38+X39+X40+X41+X42+X43+X44+X45+X46+X47+X48+X49+X50+X51+X52+X53+X54+X55+X56+X57+X58+X59+X60+X61+X62+X63+X64+X65+X66+X67+X68+X69+X70+X71+X72+X73+X74+X75+X76+X77+X78+X79+X80+X81+X82+X83+X84+X85+X86+X87+X88+X89+X90+X91+X92+X93+X94+X95+X96+X97+X98+X99+X100+X101+X102+X103+X104+X105+X106+X107+X108+X109+X110+X111+X112+X113+X114+X115+X116+X117+X118+X119+X120+X121+X122+X123+X124+X125+X126+X127+X128+X129+X130+X131+X132+X1...

...quot;,"X48","X49","X50","X51","X52","X53","X54","X55","X56","X57","X58","X59","X60","X61","X62","X63","X64","X65","X66","X67","X68","X69","X70","X71","X72","X73","X74","X75","X76","X77","X78","X79","X80","X81","X82","X83","X84",&quot...

...x48","x49","x50", "x51","x52","x53","x54","x55","x56","x57","x58","x59","x60", "x61","x62","x63","x64","x65","x66","x67","x68","x69","x70", "x71","x72","x73","x74","x75","x76","x77","x78","x79","x80", "x81","x82","x83","x84...

...ot;, "X49", "X50", "X51", "X52", "X53", "X54", "X55", "X56", "X57", "X58", "X59", "X60", "X61", "X62", "X63", "X64", "X65", "X66", "X67", "X68", "X69", "X70", "X71", "X72", "X73", "X74", "X75", "X76", "X77", "X78", "X79", "X80", "X81", "X82", "X83", &qu...

...quot;,"X48","X49","X50","X51","X52","X53","X54","X55","X56","X57","X58","X59","X60","X61","X62","X63","X64","X65","X66","X67","X68","X69","X70","X71","X72","X73","X74","X75","X76","X77","X78","X79","X80","X81","X82","X83","X84",&quot...

...X22 "TT" "AA" "TT" X31 "CT" "AG" "CT" X32 "CT" "AG" "TT" X37 "CT" "AA" "CT" X50 "TT" "AA" "CT" X66 "CC" "AA" "CC" X28 "CT" "AG" "CC" X29 "CT" "AG" "CT" X30 "CT" "GG" "CT" X56 "CT" "AG" "CC" X62...

...X6, X7, X8, X9, X10, X11, X12, X13, X14, X15, X16, X17, X18, X19, X20, X21, X22, X23, X24, X25, X26, X27, X28, X29, X30, X31, X32, X33, X34, X35, X36, X37, X38, X39, X40, X41, X42, X43, X44, X45, X46, X47, X48, X49, X50, X51, X52, X53, X54, X55, X56, X57, X58, X59, X60, X61, X62, X63, X64, X65, X66, X67, X68, X69, X70, X71, X72, X73, X74, X75, X76, X77, X78, X79, X80, X81, X82, X83, X84, X85, X86, X87, X88, X89, X90, X91, X92, X93, X94, X95, X96, X97, X98, X99, X100, theta = lambda, scale = FALSE) and get the error message Error in model.frame.default(formula = form, data = sdf) : invalid...

Hi, I was wondering how it was possible to access the actual cluster exemplars from the APResult class. Currently it only spits it out onto the terminal if you type the object but there is no other way to see which one is the examplar. Would appreciate any help. Thanks, Sachin [[alternative HTML version deleted]]