search for: modnames

...ing the AICmodavg package and using R version 2.15.1. I need help with code that is instead being read as text. Below is a subset of code... I actually have 12 models, but I am trying to get this to work for 2 below right now. Everything 'appears' to work through the line starting with Modnames. After that the code starting with aictab and beyond is recognized as text and not code. What am I doing incorrectly with the code? buco.models<-list ( ) buco.models [[1]] <- glm(P.BUCO~faverage+W15CNT, family=binomial(logit), data=AmphAIC) buco.models [[2]] <- glm(P.BUCO~diam1+W15CNT...

This adds [f]getc() and fgets() for parsing config files. Probably hard to avoid. Still trying to decide if I actually want to add system() or not. -hpa

...ta = cement ) Cand.models[[2]] <- lm ( y ~ x3 + x4, data = cement ) Cand.models[[3]] <- lm ( y ~ x1 + x2 + x1 * x2, data = cement ) Cand.models[[4]] <- lm ( y ~ x3 + x4 + x3 * x4, data = cement ) ## vector of model names Modnames <- paste("MODEL", 1:4, sep=" ") ## AICc aictab ( cand.set = Cand.models, modnames = Modnames ) However, the AICc value reported by Anderson (2008) is 32.41. The AICc value obtained using RSS value (i.e., calculating AICc "manually" fro...

Hi All, Im interested in creating a function that will convert a variable within a data.frame to a factor while retaining the original name (yes, I know that I can just: var <-factor(var) but I need it as a function for other purposes). e.g.: # this was an attempt but fails. facts <- function(meta, mod, modname = "spec") { meta$mod <- factor(meta$mod)

...e 'Elf64_Xword' + KEYFLAGS='--no-default-keyring --homedir ..' + KEYFLAGS='--no-default-keyring --homedir .. --secret-keyring ../kernel.sec' + KEYFLAGS='--no-default-keyring --homedir .. --secret-keyring ../kernel.sec --keyring ../kernel.pub' + export KEYFLAGS ++ cat modnames + for i in '`cat modnames`' + sh ./scripts/modsign/modsign.sh /var/tmp/kernel-2.6.18-92.1.17.1.el5_ArcosCom-root/lib/modules/2.6.18-92.1.17.1.el5_ArcosCom/kernel/sound/i2c/snd-cs8427.ko CentOS gpg: WARNING: unsafe permissions on homedir `..' gpg: no default secret key: secret key not av...

Hi, working on the LNT documentation I am wondering about a few things: - LNT documentation recommends to do `easy_install lnt==0.4.2dev` (in the install box on the left side of the title page). The last available version of LNT on pypy is version 0.4.0 from 2012. Are there plans to keep this up to date or should we better remove the entry and not mention pypy packages anymore? - Building the

Hi, as a followup for the signature fix for mount_vfs [1], here it is a patch series to generate automatically most of the OCaml interfaces of daemon actions. Only the Lvm and Mount modules are left with hand-written interfaces. [1] https://www.redhat.com/archives/libguestfs/2018-April/msg00059.html Thanks, Pino Toscano (3): daemon: directly use Optgroups daemon: use the structs from the

I'd be fine pulling the pypi (sic) entry, shall I make it so? - Daniel On Tue, Jul 18, 2017 at 11:06 AM Chris Matthews <chris.matthews at apple.com> wrote: > Yep, we should pull that package down, or start to update it. > > The docs builds work for me. Is it possible that is not in your venv or > something like that? > > > On Jul 18, 2017, at 10:48 AM, Matthias

Hi, On 2020-09-25 16:38:41 -0700, Andres Freund via llvm-dev wrote: > On 2020-09-24 16:34:30 -0700, Lang Hames wrote: > > If anyone wants to check out the OrcV1 removal branch and provide feedback > > now is the time. Otherwise I will aim to land the work in the mainline > > early next week. > > I'm trying to get it to work with postgres. Unfortunately this week

plain text document attachment (lguest64-debug-utils.patch) This patch contains some nice features used to debug the lguest64 guest. It has a way to print page tables for either the host or the guest. It incorporates kallsyms, and can do a nice back trace of a guest when it crashes. The guest needs kallsyms obviously compiled in. Note: This code needs to be fixed to be more secure! Implements

plain text document attachment (lguest64-debug-utils.patch) This patch contains some nice features used to debug the lguest64 guest. It has a way to print page tables for either the host or the guest. It incorporates kallsyms, and can do a nice back trace of a guest when it crashes. The guest needs kallsyms obviously compiled in. Note: This code needs to be fixed to be more secure! Implements

I updated the docs to show a pip/svn install like this: pip install svn+http://llvm.org/svn/llvm-project/lnt/trunk <svn+http://llvm.org/svn/llvm-project/lnt/trunk> > On Jul 18, 2017, at 11:24 AM, Kristof Beyls <kristof.beyls at arm.com> wrote: > > >> On 18 Jul 2017, at 20:21, Daniel Dunbar <daniel at zuster.org <mailto:daniel at zuster.org>> wrote:

Starting with nbdkit 1.16, Python >= 3.3 will be required. Python 2 reaches end of life on 2020-01-01: https://python3statement.org/ https://pythonclock.org/ Debian oldoldstable and RHEL 7 have Python 3.4 and 3.6 respectively, so it seems pointless to try to support Python < 3.3 which lacked support for PyUnicode_AsUTF8. --- README | 13 +++++++------ configure.ac

What is the official syntax for pulling multiple sources from a daemon? In analogy to a remote shell, I expected this to work: rsync rsync://matt@mattlaptop2:3141/module/'foo bar' dest/ But it doesn't; the daemon tried to access a file 'foo bar' with a space in its name. Using a newline like this does work because the newline becomes an argument delimiter in the daemon

This is taken from the work I did on lguest64. When killing a guest, we read the guest stack to do a nice back trace of the guest and send it via printk to the host. So instead of just getting an error message from the lguest launcher of: lguest: bad read address 537012178 len 1 I also get in my dmesg: called from [<c0405f30>] show_trace_log_lvl+0x1a/0x2f [<c04069aa>]

This is taken from the work I did on lguest64. When killing a guest, we read the guest stack to do a nice back trace of the guest and send it via printk to the host. So instead of just getting an error message from the lguest launcher of: lguest: bad read address 537012178 len 1 I also get in my dmesg: called from [<c0405f30>] show_trace_log_lvl+0x1a/0x2f [<c04069aa>]

Add a way to generate OCaml interfaces for a whilelist of modules in the daemon that implement APIs: this makes sure that for them the interface of each function matches the actual API specified in the generator. Only the modules specified in a list are generated for now, although this coverts almost all the daemon APIs implemented in OCaml. --- .gitignore | 15 ++++++++++

Add a way to generate OCaml interfaces for all the modules in the daemon that implement APIs: this makes sure that for them the interface of each function matches the actual API specified in the generator. --- .gitignore | 17 +++++++++++ daemon/blkid.mli | 19 ------------ daemon/btrfs.mli | 20 ------------- daemon/devsparts.mli | 25 ---------------- daemon/file.mli | 19

This patch proposes to drop support for Python 2 in nbdkit. Rather than abruptly drop it everywhere, my proposal is that we point people to nbdkit 1.14 (the current stable version) if they want to continue with Python 2 plugins, while gently reminding them of the upcoming Python 2.7 end of life announcement. Libnbd never supported Python 2. Libguestfs in theory supports Python 2 but I dropped

Dear Rexperts: (R 2.0.1 on Windows XP Pro) Is the following problem unique to my setup? If it's a known problem, I didn't see it at http://bugs.r-project.org/ nor find discussion in the archives. plot(1:10) loc <- c(5, 6) text(loc, labels = "a") Produces expected results according to ?xy.coords. plot(1:10) loc <- list(x = 5, y = 6) text(loc, labels = "a") No