search for: aml

...L.17 ALL.18 ALL.19 ALL.20 ALL.21 ALL.22 2 -92 -113 -107 -117 -476 -81 -44 17 -144 -247 -74 3 -119 -147 -72 -219 -213 -150 -51 -229 -199 -90 -321 4 -31 -118 -126 -50 -18 -119 100 79 -157 -168 -11 ALL.23 ALL.24 ALL.25 ALL.26 AML AML.1 AML.2 AML.3 AML.4 AML.5 AML.6 AML.7 2 -120 -81 -112 -273 -20 7 -213 -25 -72 -4 15 -318 3 -263 -150 -233 -327 -207 -100 -252 -20 -139 -116 -114 -192 4 -114 -85 -78 -76 -50 -57 136 124 -1 -125 2 -95 AML.8 AML.9 AML.10 ALL.2...

Hi there, I have a question about one command sentence when I follow the example in the book of "Survival analysis in S": > aml1<-aml[aml$group==1] but I got the error warning: NULL data frame with 23 rows Thus, I couldn't keep going on the next command: esf.fit<-survfit(Surv(aml1,status)~1). and also when I try > aml1<-aml[aml$group==1,] > aml1 I got [1] time status x...

...ovmf_acpi_build_tables(void) > > > .dsdt_anycpu = dsdt_anycpu, > > > .dsdt_anycpu_len = dsdt_anycpu_len, > > > .dsdt_15cpu = NULL, > > > - .dsdt_15cpu_len = 0 > > > + .dsdt_15cpu_len = 0, > > > + .aml_ej0_name = NULL, > > > + .aml_adr_dword = NULL, > > > + .aml_ej0_name_len = 0, > > > + .aml_adr_dword_len = 0, > > > > I don''t see why you''re adding these. > > > Insurance purposes is that just initialize the str...

...the modified example from the help page of survSplit. The original works, as expected. If, however, a Surv object is added to the data.frame, each record gets doubled. Is there some solution other than avoiding Surv objects in data.frames? Thanks, Heinz require(survival) ## from the help page aml3<-survSplit(aml,cut=c(5,10,50),end="time",start="start", event="status",episode="i") summary(aml) summary(aml3) coxph(Surv(time,status)~x,data=aml) ## the same coxph(Surv(start,time,status)~x,data=aml3) ## added to show doubling of records aml.so...

Hi I am Aadhithya I am trying to write a code to classify microarray data (AML and ALL) using SVM in R my code goes like this : library(e1071) train<-read.table("Z:/Documents/train.txt",header=T); test<-read.table("Z:/Documents/test.txt",header=T); cl <- c(c(rep("ALL",10), rep("AML",10))); model<- svm(train,cl); pred <-...

Hello: Using the built-in dataset aml as an example: data(aml) If I use instead dummy variables: aml$x1 = (aml$x=="maintained")aml$x2 = (aml$x=="unmaintained") and I want to plot the survival curve using x1, x2, and I just want the 2 levels, rather than 4 curves from: fit <- survfit(Surv(time, status) ~ x1+...

...visó la última vez: > 0 = Buen estado > 1 = Para tirar > > Y utiliza el método kaplan-meier: > > library(survival) > KM <- survfit(Surv(DATO$TIEMPO, DATOS$ESTADO) ~ 1) > summary(KM) > plot(KM) > > Un ejemplo: > > > library(survival) > > AML.KM <- survfit(Surv(aml$time, aml$status) ~ 1) > > summary(AML.KM) > Call: survfit(formula = Surv(aml$time, aml$status) ~ 1) > > time n.risk n.event survival std.err lower 95% CI upper 95% CI > 5 23 2 0,9130 0,0588 0,8049 1,000 > 8 21...

On Wed, Nov 20, 2019 at 10:36:31PM +0100, Karol Herbst wrote: > with the branch and patch applied: > https://gist.githubusercontent.com/karolherbst/03c4c8141b0fa292d781badfa186479e/raw/5c62640afbc57d6e69ea924c338bd2836e770d02/gistfile1.txt Thanks for testing. Too bad it did not help :( I suppose there is no change if you increase the delay to say 1s?

Dear all, I run the example of "censboot" contained in "boot" package. But, I can't find the confidence interval of the resulted "censboot" object. Any idea ? > aml.fun <- function(data) { + surv <- survfit(Surv(time, cens)~group, data=data) + out <- NULL + st <- 1 + for (s in 1:length(surv$strata)) { + inds <- st:(st+surv$strata[s]-1) + md <- min(surv$time[inds[1-surv$surv...

Buenas, Como pudeo calcular el tiempo de vida? Os cuento, tengo una serie de cuchillas y quiero ver el consumo de las mismas y he pensado en hacer un estudio por tiempo de vida. No se como hacerlo con R Gracias Jesús [[alternative HTML version deleted]]

...issues with delays:) Disable rpm for the Nvidia device (control = on). 4. modprobe nouveau. The above test with v4.6 + 4 pci/pm patches (8b71f565) gives: 50.245795 MXM: GUID detected in BIOS 50.245948 nseval-0227 ns_evaluate : **** Execute method [\_SB.PCI0.GFX0._DSM] at AML address ffffc90000013b11 length 492 50.246016 ACPI Warning: \_SB.PCI0.GFX0._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20160108/nsarguments-95) 50.246044 nseval-0227 ns_evaluate : **** Execute method [\_SB.PCI0.GFX0._DSM] at AML address ffffc90000...

...are called > > > > > > > > > PEG, PCI Express Graphics, ports), and the PCH side. I think the IP is > > > > > > > > > still the same. > > > > > > > > > > > > > > > > > > > Also some custom AML-based power management is involved and that may > > > > > > > > > > be making specific assumptions on the configuration of the SoC and the > > > > > > > > > > GPU at the time of its invocation which unfortunately are not known to > >...

Dear mailing list, I tried to run the example for the conditional bootstap written in the help file of censboot. I got the following result: STRATIFIED CONDITIONAL BOOTSTRAP FOR CENSORED DATA Call: censboot(data = aml, statistic = aml.fun, R = 499, F.surv = aml.s1, G.surv = aml.s2, strata = aml$group, sim = "cond") Bootstrap Statistics : original bias std. error t1* 31 Inf NaN t2* 23 -2.058116 8.670602 ***** I don't know if there is something in the g...

...Too bad it did not help :( I suppose there is no > > change if you increase the delay to say 1s? > > Well, look at the original patch in this thread. > > What it does is to prevent the device (GPU in this particular case) > from going into a PCI low-power state before invoking AML to power it > down (the AML is still invoked after this patch AFAICS), so why would > that have anything to do with the delays? > > The only reason would be the AML running too early, but that doesn't > seem likely. IMO more likely is that the AML does something which > canno...

...: > > > > > On Wed, Nov 20, 2019 at 11:18 AM Mika Westerberg > > > > > <mika.westerberg at intel.com> wrote: > > > > > > > > [cut] > > > > > > > > > > > Oh, so does it look like we are trying to work around AML that tried > > > > > to work around some problematic behavior in Linux at one point? > > > > > > > > Yes, it looks like so if I read the ASL right. > > > > > > OK, so that would call for a DMI-based quirk as the real cause for the > > &...

...oo bad it did not help :( I suppose there is no > > change if you increase the delay to say 1s? > > Well, look at the original patch in this thread. > > What it does is to prevent the device (GPU in this particular case) > from going into a PCI low-power state before invoking AML to power it > down (the AML is still invoked after this patch AFAICS), so why would > that have anything to do with the delays? Yes, I know what it does :) I was just thinking that maybe it's still the link that does not come up when we go back to D0 I guess that's not the case here....

...kaplan-meier: > > > > > > library(survival) > > > KM <- survfit(Surv(DATO$TIEMPO, DATOS$ESTADO) ~ 1) > > > summary(KM) > > > plot(KM) > > > > > > Un ejemplo: > > > > > > > library(survival) > > > > AML.KM <- survfit(Surv(aml$time, aml$status) ~ 1) > > > > summary(AML.KM) > > > Call: survfit(formula = Surv(aml$time, aml$status) ~ 1) > > > > > > time n.risk n.event survival std.err lower 95% CI upper 95% CI > > > 5 23 2 0,9130 0,...

...; > > > > Exactly. Intel hardware has PCIe ports on CPU side (these are called > > > > > PEG, PCI Express Graphics, ports), and the PCH side. I think the IP is > > > > > still the same. > > > > > > > > > > > Also some custom AML-based power management is involved and that may > > > > > > be making specific assumptions on the configuration of the SoC and the > > > > > > GPU at the time of its invocation which unfortunately are not known to > > > > > > us. > > >...

...s is a PCIe port, but its location within the SoC may matter. > > > > Exactly. Intel hardware has PCIe ports on CPU side (these are called > > PEG, PCI Express Graphics, ports), and the PCH side. I think the IP is > > still the same. > > > > > Also some custom AML-based power management is involved and that may > > > be making specific assumptions on the configuration of the SoC and the > > > GPU at the time of its invocation which unfortunately are not known to > > > us. > > > > > > However, it looks like the AML...

Dear experts, I would like to know how to plot the log-minus-log plot for survival analysis (to check the proportional assumption) in R. Using the AML example. fit <- survfit(Surv(time, status) ~ x, data=aml) length(fit$surv) #20 as the length of fit$surv is shorter than aml$x and aml$time. I don't know how to plot. Thank you. Regards, CH -- CH Chan Research Assistant - KWH http://www.macgrass.com