similar to: "deparse" with "nlines" argument produces empty elements (PR#13299)

Hi, I have data for one dependent variable and multiple independent variables y = b0 + b1*x1 + b2*x2 + ... I want to a list of all models that have some subset of the independents (just x1 x2, and not x3, etc.) and their corresponding BIC values. Is there a pre-existing function that does this? I saw that you can calculate individual BIC values using 'lm' and something like AIC(lm1, k

I have spent a fair amount of time looking for a package that is automated to run glm (binomial) regression models with all possible subsets of my independent variables. Something akin to Lumley's "leaps" package, but can be applied to glms, not just lms; or something similar to Stata's brute force "tryem" function? If anyone can point me in the right direction I

Recently, I have been working with some data that look like two overlapping gaussian distributions. I would like to either 1) determine the mean and SD for each of the two distributions OR 2) get some (bayesian ?) statistic that estimates how likely an observation is to belong to the left-hand or right-hand distribution In case I'm using the wrong language, my data looks something like

Hello, I have a problem with readLines. I have a data file with many informations added with a different number of measurments (example at the end). I only want to read the measurments witch start with "START OF HEIGHT DATA" and end with "END OF HEIGHT DATA". The difficulty is: -I want to read the file with "readLines", because the measurments have letters and

<div class="socmaildefaultfont" dir="ltr" style="font-family:Arial, Helvetica, sans-serif;font-size:9pt" ><div dir="ltr" >Hi all,</div> <div dir="ltr" >I'm very excited to be able to share this with everyone. </div> <div dir="ltr" > </div> <div dir="ltr" >IBM announced this

Hi, I am wondering why we dont support PPC32 LE? Here is the output of llvm-mc --version, in which only PPC32, PPC64 & PPC64LE are supported. $ llvm-mc --version LLVM (http://llvm.org/): LLVM version 3.6.2 Optimized build with assertions. Built Aug 2 2015 (11:39:46). Default target: x86_64-apple-darwin15.4.0 Host CPU: core-avx2 Registered Targets: aarch64 - AArch64

Hello, I didn't try 6.02-pre15, I will do and I will post the results, my keyboard is a PS/2 model, the "legacy USB storage option" is enabled, I tried also an USB keyboard but there is no change, so it's not a keyboard problem, it probably something in syslinux ( ldlinux.sys ? ) who create a serious bug with my motherboard, I tried also with a USB HDD ( not a flash drive )

----- Original Message ----- > From: "Eric Christopher" <echristo at gmail.com> > To: "Tim Shen" <timshen at google.com>, llvm-dev at lists.llvm.org, "Hal > Finkel" <hfinkel at anl.gov>, "Kit Barton" <kbarton at ca.ibm.com> > Sent: Wednesday, February 10, 2016 6:59:50 PM > Subject: Re: [llvm-dev] [PPC] Linker fails on

I'll come up with a address-space-based proof of concept. On Wed, Feb 10, 2016, 17:05 Eric Christopher <echristo at gmail.com> wrote: > On Wed, Feb 10, 2016 at 5:04 PM Hal Finkel <hfinkel at anl.gov> wrote: > >> >> ------------------------------ >> >> *From: *"Eric Christopher" <echristo at gmail.com> >> *To: *"Tim

I found a bit weird to use address space for this, since the offset of getting stack_guard in TCB is, unfortunately, negative: https://github.com/gcc-mirror/gcc/blob/master/gcc/config/rs6000/linux64.h#L610 In my understanding an address space is referring to a segment register (-on powerpc 32bit; or SLB entry on powerpc 64bit?) with a non-negative offset value, so that it's actually accessing

lvm 3.7.0 treats pentium dual core ( cpu family 6 model 23 ) as "penryn" cpu, which triggers a serious bug : - crashs in openGL programs when llvm is used by mesa package, llvm will produces binary code with SSE4 instructions, which is not compatible with pentium dual core, because this CPU doesn't support SSE4 instructions ( bad cpu opcodes ), with llvm 3.6.2 this bug doesn't

Odette Gaston <odette.gaston <at> gmail.com> writes: > > Dear all, > > I have a problem with accessing class attributes. > I was unable to solve this > yet, but someone may know how to solve it. My best guess at your immediate problem (doing things by hand) is that you're not using the whole vector. From your example: Delta <- c(m1 = 0, m2 = 1.8, m3 =

This is probably best viewed in the context of other issue with displaying calls, such as issues arising from calls constructed in non-standard evaluation contexts. Might be good to move to a wishlist item in bugzilla. Best, luke On Sat, 13 Jul 2019, brodie gaslam via R-devel wrote: > When large calls cause errors R may stall for extended periods.? This > is particularly likely to happen

I have just tried the 6.02-pre15 version of syslinux and good news : the bug is fixed with this version, now I can boot without system freezes with my motherboard gigabyte GA-P31-DS3L Le 02/08/2013 11:53, Barto a ?crit : > Hello, > > I didn't try 6.02-pre15, I will do and I will post the results, >

On Aug 2, 2013 3:45 AM, "Barto" <mister.freeman at laposte.net> wrote: > > Hello, > > I notice a bug in syslinux 6.01 ( bios version ) when I install it in a > USB flash drive ( FAT32 partition ) and when I want to boot this USB > flash drive with a gigabyte motherboard ( GA-P31-DS3L ), > > I setup my usb flash drive ( 4 Gb ) like this in windows XP : >

hi, I'm using the sem package, and I want to make sure I'm interpreting the output correctly. Here is an excerpt of my output. When I report the MWD error, should I say that 59% of the variation in MWD is not explained by the model, or that 59% of the variation is explained, or something entirely different. Parameter Estimates Estimate Std Error z value Pr(>|z|)

Better to add this to the wishlist item. This all needs to be looked at together, and nothing is likely to happen until after vacation/conference season. It will disappear from everyone's radar if it is just in R_devel. Best, luke On Sun, 14 Jul 2019, brodie gaslam wrote: > Luke, thanks for considering the issue.? I would like to > try to separate the problem into two parts, as I

There was a GSoC project in 2016, final report at https://docs.google.com/document/d/1v-R7gB7Or4bPn0LW7d-yb1yla8jK3DVmTJNFVNYNu6k Google doesn't show a lot of activity since. Has anyone taken this work further / put it near production? I'm interested in removing register spills around functions that are known to not clobber said registers. Thanks! Jon -------------- next part

When large calls cause errors R may stall for extended periods.? This is particularly likely to happen with `do.call`, as in this example with a 24 second stall: ??? x <- runif(1e7) ??? system.time(do.call(paste0, list(abs, x)))? # intentional error ??? ## Error in (function (..., collapse = NULL)? : ??? ##?? cannot coerce type 'builtin' to vector of type 'character' ??? ##

Dear list, When calling R from C, what appears like a spurious error can be triggered during the execution of chisq.test(x, y). This is happening when the following conditions are met: - x and y are "anonymous" C-level R vectors (they do not have a symbol), but they are protected from garbage collection - x and y are "not too small" (it was experienced as soon as they are