search for: stat2

..."Stop2") C.df<-data.frame(cbind(c0,c1,c2,c3,c4)) colnames(C.df)<-c("c0","c1","c2","c3","c4") C.df$c5<-paste(C.df$c3,C.df$c4,sep="-") C.df # NEEDED RESULTS # needed result # for Stat1-Stop1: mean(20,30,40,50) # for Stat2-Stop2: mean(c(10,60,20,30,40,50,30,10,0,NA,20,10.3444), na.rm=T) #mean: c1 c3 c4 c5 20 Start1 Stop1 Start1-Stop1 25.48585 Start2 Stop2 Start2-Stop2 #sum # for Stat1-Stop1: sum(20,30,40,50) # for Stat2-Stop2: sum(c(10,60,20,30,40,50,30,10,0,NA,20,10.3444), na...

...dlib.h> #include <unistd.h> +#include <mntent.h> +#include <sys/stat.h> +#include <sys/types.h> #include "daemon.h" #include "actions.h" +static char* +get_mount_point (const char *device) +{ + FILE *fp; + struct mntent *m; + struct stat stat1, stat2; + char *path; + + if (stat (device, &stat1) == -1) { + reply_with_perror ("stat: %s", device); + return NULL; + } + + /* NB: Eventually we should aim to parse /proc/self/mountinfo, but + * that requires custom parsing code. + */ + fp = setmntent ("/proc/mounts&quo...

...e we are passed matches any of them. - * - * Note use of 'stat' instead of 'lstat' so that symlinks are fully - * resolved. - *) -let lv_canonical device = - let stat1 = stat device in - let lvs = lvs () in - try - Some ( - List.find ( - fun lv -> - let stat2 = stat lv in - stat1.st_rdev = stat2.st_rdev - ) lvs - ) - with - | Not_found -> None diff --git a/daemon/lvm.mli b/daemon/lvm.mli index e9a6faeca..592168433 100644 --- a/daemon/lvm.mli +++ b/daemon/lvm.mli @@ -17,13 +17,3 @@ *) val lvs : unit -> string list - -val lv_...

...d (that states the exact time this happened from the stop variable). By this I mean dat2 that looks like,   id <- rep(a, c(3,2,3)) sta2<- c(1,1,NA,1,NA,1,NA,NA) g2<- c(0,0,NA,0,NA,0,NA,NA) stop2 <- c(1,2,NA,2,NA,1,NA,NA) d <- c(4,4,NA,4,NA,1.5,NA,NA)   dat2 <- data.frame(id=id, stat2=sta2, g2=g2,stop2=stop2,d=d).   Thank you very much!   John [[alternative HTML version deleted]]

...obust z (Intercept) 0.411995251 0.174052364 2.36707644 0.131632816 3.12988253 TR8 -0.001154422 0.021191593 -0.05447549 0.011807163 -0.09777305 TR9 0.019559907 0.024379471 0.80231056 0.008993803 2.17482050 TR11 -0.041092894 0.021609580 -1.90160537 0.015384050 -2.67113620 STAT2 0.023886745 0.014219390 1.67987130 0.013543550 1.76369899 STAT3 0.045749728 0.016844262 2.71604237 0.012862504 3.55682917 temp -0.020141682 0.008819798 -2.28368975 0.006851784 -2.93962600 eta 0.008021081 0.001465212 5.47434944 0.001129986 7.09838725 Estimated Sc...

...const char *device) > +{ This function now exists in daemon/mount.c and here. It should be shared. Just make the function in daemon/mount.c non-static, and declare it in daemon/guestfsd.h, and you don't need the copy. > + FILE *fp; > + struct mntent *m; > + struct stat stat1, stat2; > + char *path; > + > + if (stat (device, &stat1) == -1) { > + reply_with_perror ("stat: %s", device); > + return NULL; > + } > + > + /* NB: Eventually we should aim to parse /proc/self/mountinfo, but > + * that requires custom parsing code. &gt...

Hi, all What I want to do is to locate the range of a for-loop statement in a binary. For example, given a for-loop statement belows, for (stat1; stat2; stat3) { /* do something */ } Is it possible to get information about the range (binary address) of the above for-loop, say, 0x0100 - 0x0120. One idea comes up in my mind is adding passes to retrieve such information in LLVM, then use llvm-gcc to compile the code. Any suggestion appreci...

Hi Irucka, I tried it and was able to plot it without any errors.? Here, your code indicates you need two lines. temper[[i]][1] ?temper[[1]][1] # which is the column 1. ? Month 1???? 1 2???? 2 3???? 3 ?temper[[1]][2] #? Data1 #1?? 1.5 #2? 12.3 #3? 11.4 Suppose I use names(temper) instead of seq_along(temper) pdf("irucka.pdf") ?lapply(names(temper),function(i)

...read the data from the website and then peform maxNR on the function, F. Btw the version of R being used is "RGui for Windows" if it helps to know this. R-code below: library(maxLik) > require(maxLik) > > x <- > read.table('http://www.math.ku.dk/kurser/2008-09/blok4/stat2/doku/data/Eksempel_6_3.txt', > header = TRUE); > t <- log(x$Koncentration); > X <- x$Status; > > p <- function(a,b) exp(a+b*t)/(1+exp(a+b*t)); > S <- sum(X); > SP <- sum(t*X); > > F <- function(a,b) { + c(sum(p(a,b)) - S, + sum(t*p(a,b))...

...ttp://llvm.org/docs/SourceLevelDebugging.html for an overview. Regards, -Jim On Apr 26, 2011, at 7:57 PM, 陳韋任 wrote: > Hi, all > > What I want to do is to locate the range of a for-loop statement in > a binary. For example, given a for-loop statement belows, > > for (stat1; stat2; stat3) { > /* do something */ > } > > Is it possible to get information about the range (binary address) > of the above for-loop, say, 0x0100 - 0x0120. > > One idea comes up in my mind is adding passes to retrieve such > information in LLVM, then use llvm-gcc to compil...

https://bugzilla.redhat.com/show_bug.cgi?id=755729 This bug reports that the error message printed by the resize2fs API calls (which comes directly from the resize2fs command) says: Please run 'e2fsck -f /dev/vda1' first. That command is not possible from guestfish (where it would be 'e2fsck-f' or 'e2fsck ... forceall:true'). Fixing that bug caused this bug:

Hi, as a followup for the signature fix for mount_vfs [1], here it is a patch series to generate automatically all the OCaml interfaces of daemon actions. [1] https://www.redhat.com/archives/libguestfs/2018-April/msg00059.html Thanks, Pino Toscano (5): daemon: directly use Optgroups daemon: use the structs from the Structs module daemon: move Lvm.lv_canonical to new Lvm_utils module

Dear all I try to persuade if statement in my function to work as I want (but I am not very successful:( My question is why my function with if statement is evaluated correctly in case of atomic variables and incorrectly in case of vector variables. Here is an example: #function with if statement fff <- function(otac,sklon) { test <- (otac *

...an overview. > > Regards, > -Jim > > On Apr 26, 2011, at 7:57 PM, 陳韋任 wrote: > >> Hi, all >> >> What I want to do is to locate the range of a for-loop statement in >> a binary. For example, given a for-loop statement belows, >> >> for (stat1; stat2; stat3) { >> /* do something */ >> } >> >> Is it possible to get information about the range (binary address) >> of the above for-loop, say, 0x0100 - 0x0120. >> >> One idea comes up in my mind is adding passes to retrieve such >> information in...

...t.c:201: warning: `return' with a value, in function returning void tpkt.c:205: error: `t' undeclared (first use in this function) tpkt.c: In function `tpkt_rx_packet': tpkt.c:241: warning: implicit declaration of function `decode_open_type' tpkt.c:211: warning: unused variable `stat2' tpkt.c:212: warning: unused variable `i' tpkt.c:213: warning: unused variable `j' udptl.c: In function `udptl_process_packet': udptl.c:150: warning: no return statement in function returning non-void udptl.c: In function `udptl_build_packet': udptl.c:541: warning: i...

Hello, ? I believe that in R, it is not possible to analyze mixed effect-models when the distribucion is not gaussian (p.e. binomial or poisson), isn't? ? Somebody can suggest me alternative? ? thanks ? xavi ? -.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.- r-help mailing list -- Read http://www.ci.tuwien.ac.at/~hornik/R/R-FAQ.html Send "info",

...{ /* "/foo/bar" */ - dirname = strndup (orig_filename, p-orig_filename); - basename = p+1; - - /* If the parent directory is a symlink to another directory, then - * we want to look up the target directory. (RHBZ#698089). - */ - struct stat stat1, stat2; - if (lstat (dirname, &stat1) == 0 && S_ISLNK (stat1.st_mode) && - stat (dirname, &stat2) == 0 && S_ISDIR (stat2.st_mode)) { - char *new_dirname = malloc (PATH_MAX+1); - ssize_t r = readlink (dirname, new_dirname, PATH_MAX+1); - if (r == -1)...

I think this fixes everything mentioned: - Added the Optgroups module as suggested. - Remove command temporary files. - Replace command ~flags with ?fold_stdout_on_stderr. - Nest _with_mounted function. - Rebase & retest. Rich.

v1 was posted here: https://www.redhat.com/archives/libguestfs/2017-July/msg00098.html This series now depends on two small patches which I posted separately: https://www.redhat.com/archives/libguestfs/2017-July/msg00207.html https://www.redhat.com/archives/libguestfs/2017-July/msg00209.html v1 -> v2: - Previously changes to generator/daemon.ml were made incrementally through the patch

Previously posted as part of the mega utilities/inspection series here: https://www.redhat.com/archives/libguestfs/2017-June/msg00232.html What I've done is to extract just the parts related to rewriting daemon APIs in OCaml, rebase them on top of the current master, fix a few things, and recompile and test everything. Rich.