search for: 3.8e

Dear All, Please help me understand why timestamps in logs are different from those in nsd-control zonestatus output: served-serial: "2024022603 since 2024-02-27T08:07:51" commit-serial: "2024022603 since 2024-02-27T08:07:51" Feb 26 18:47:34 slave-server nsd[780]: zone testzone.test. received update to serial 2024022603 at 2024-02-26T18:47:33 from

Dear list members, I am trying to estimate parameters of the AR(1)-GARCH(1,1) model. I have one additional dummy variable for the AR(1) part. First I wanted to do it using garchFit function (everything would be then estimated in one step) however in the fGarch library I didn't find a way to include an additional variable. That would be the formula but, as said, I think it is impossible to add

The following fit does not make sense to me, please, correct me if I have a logical error. > moddowsn Call: coxph(formula = Surv(start, stop, resp) ~ sn + matfac2, data = coxsn1, method = "efron") coef exp(coef) se(coef) z p sn2 0.0497 1.051 0.02030 2.450 1.4e-02 sn3 -0.0532 0.948 0.02038 -2.610 9.0e-03 sn4 -0.0410 0.960

Hi Peter, NSD processes updates in batches. xfrd receives the [AI]XFR and schedules a reload for the main process, which in turn forks new serve children. The served-serial is updated after main reports success, the commit-serial (update written to disk) is updated before the reload (to explain the serials). The difference in timestamp can be explained by the fact that NSD looks up if the serial

I was testing Ilia's patches for ddx, and while they definitely helped for Xorg itself, qemu still eats a lot of CPU if launched like this qemu-system-x86_64 -cdrom ~/Downloads/ISO/slax-English-US-7.0.8-x86_64.iso -m 1G -display sdl,gl=on -enable-kvm and left for few hours. top - 07:38:01 up 18:05, 2 users, load average: 2,00, 1,89, 1,83 Tasks: 224 total, 3 running, 221 sleeping, 0

Hi Jeroen, I just realised that the version I use is very old -- 4.1. So first what I should do -- updating it and only then come here , asking for clarification. ??, 27 ????. 2024??. ? 14:19, Jeroen Koekkoek <jeroen at nlnetlabs.nl>: > Hi Peter, > > NSD processes updates in batches. xfrd receives the [AI]XFR and > schedules a reload for the main process, which in turn forks

Hi, I am having trouble with the survival library, particualrily the coxph function. the following works coxph(jtree9$cph.call,z,rep(1,dim(z)[1])) Call: coxph(formula = jtree9$cph.call, data = z, weights = rep(1, dim(z)[1])) coef exp(coef) se(coef) z p SM 0.2574 1.294 0.0786 3.274 1.1e-03 Sex -0.1283 0.880 0.1809 -0.709

Hi all, I try to represent a multiple curve graphic where the x-axis is the temperature and the different y-axes are the different X (X22,X43,X44...) some X corresponds to the same molecule (22 and 44 are for CO2 for instance) so I use the same colour for them. I wanna mix the linetype with the colour to be able to visually see the difference between X43 and X45 The best I have done up to now

Dear all, Does the frailty.object$history[[1]]$theta returns the Variance of random effect? Why is the value different? Here is an example with kidney data: > library(survival) > data(kidney) > frailty.object<-coxph(Surv(time, status)~ age + sex + disease + frailty(id), kidney) > frailty.object Call: coxph(formula = Surv(time, status) ~ age + sex + disease + frailty(id), data

All, I have some code that I have been working on that crashes R (1.8.1 on MacOS X installed from source). Here are excerpts of the code and data structures. When the lists that I am using to construct the data.frame are truncated (shortened), R catches the differing rows and warns. However, when the entire lists are used (I haven't looked for an exact breakpoint or for a particular list

The DDX eating CPU isn't intrinsically bad. Did you check where perf says the CPU time is going? Could be doing copies/etc. On Mon, Aug 17, 2020 at 12:52 AM Andrew Randrianasulu <randrianasulu at gmail.com> wrote: > > I was testing Ilia's patches for ddx, and while they definitely helped for Xorg itself, > qemu still eats a lot of CPU if launched like this > >

Dear List, i am trying to produce a 3d plot using wireframe using the code: wireframe(Residuals_FD ~ Elevation * Temperature, data = data2, scales = list(arrows = FALSE), drape = TRUE, colorkey = TRUE) As you can see when the code (using the data below) is run the plot area is set-up correctly but the actual surface is missing? Any help would be greatly appreciated. Chris #data Elevation

> version _ platform i686-pc-linux-gnu arch i686 os linux-gnu system i686, linux-gnu status major 1 minor 7.1 year 2003 month 06 day 16 language R Bug: integrate(f,lower,upper,extra_args) where f <- function(x,extra_args) { body } integrate doesn't pass the extra arguments when calling f. As a first check of this finding I integrated dnorm from

I rebuild mesa with debug symbols, and now top functions using CPU looks like this: CPU: AMD64 family15h, speed 3800 MHz (estimated) Counted CPU_CLK_UNHALTED events (CPU Clocks not Halted) with a unit mask of 0x00 (No unit mask) count 100000 samples % image name symbol name ------------------------------------------------------------------------------- 222978 45.1489