similar to: biglm 0.4

New versions of leaps and biglm are percolating through CRAN. The new version of biglm fixes a bug in sandwich standard errors with weights, and adds predict(), deviance() and AIC() methods [based on code from Christophe Dutang]. The new version of leaps adds a regsubsets() method for biglm objects, so that the subset selection algorithms can be run efficiently on large data sets. -thomas

New versions of leaps and biglm are percolating through CRAN. The new version of biglm fixes a bug in sandwich standard errors with weights, and adds predict(), deviance() and AIC() methods [based on code from Christophe Dutang]. The new version of leaps adds a regsubsets() method for biglm objects, so that the subset selection algorithms can be run efficiently on large data sets. -thomas

If a package defined an S3 generic and an S4 generic for the same function (so as to add methods for S4 classes to the existing code), how do I set up the namespace to have them exported? With import(stats) exportMethods(bigglm) importClassesFrom(DBI) useDynLib(biglm) export(biglm) export(bigglm) in NAMESPACE, the S3 generic is not exported. > methods("bigglm") [1] bigglm.RODBC*

Dear Thomas, Thank you, yes, that sounds good, and I take the point about integer overflow. Various questions: (a) Is there some way I can try out the routine with this modification? (I am on a Linux system where I am just a user - I cannot install new versions of software myself) ? (b) Is there a reference you can give me to a published paper where the method being used to compute the

I've fixed this by adding 0.5/mn to q. The problem (at least in principle) with multiplying them all up is integer overflow. By the time 0.5/mn underflows to zero, missing one value in the distribution won't matter. -thomas On Fri, 18 Dec 2009, David John Allwright wrote: > Dear Thomas, Right, thank you. Yes, I haven't looked at the source code > (because I don't

Dear R-help This is a follow-up to my previous post here: http://groups.google.com/group/r-help-archive/browse_thread/thread/d9b6f87ce06a9fb7/e9be30a4688f239c?lnk=gst&q=dobomode#e9be30a4688f239c I am working on developing an open-source automated system for running batch-regressions on very large datasets. In my previous post, I posed the question of obtaining VIF's from the output of

Version 3.3 of "survey" is percolating through CRAN. Since the last announcement on this list, version 2.9, the main additions are calibration estimators: linear, bounded linear, raking ratio, bounded raking ratio, logit. Other updates and bug fixes are described in http://faculty.washington.edu/tlumley/survey/NEWS -thomas Thomas Lumley Assoc. Professor,

Version 3.3 of "survey" is percolating through CRAN. Since the last announcement on this list, version 2.9, the main additions are calibration estimators: linear, bounded linear, raking ratio, bounded raking ratio, logit. Other updates and bug fixes are described in http://faculty.washington.edu/tlumley/survey/NEWS -thomas Thomas Lumley Assoc. Professor,

Hi, I do have it installed on 2 Macs as well (OS X 10.2.8 and 10.3.7) and what I need does work, however if you do the command check routine some problems will likely be revealed. At least there were problems for me. Denis Le 08 févr. 2005, à 12:23, r-help-request@stat.math.ethz.ch a écrit : > De: Don MacQueen <macq@llnl.gov> > Date: 07 février 2005 16:05:14 GMT+01:00 > À:

Hi Sir, Thanks for making package available to us. I am facing few problems if you can give some hints: Problem-1: The model summary and residual deviance matched (in the mail below) but I didn't understand why AIC is still different. > AIC(m1) [1] 532965 > AIC(m1big_longer) [1] 101442.9 Problem-2: chunksize argument is there in bigglm but not in biglm, consequently,

Thomas, that's a good point. I was thinking of anscombe[x1::y1] making it clear which one, but you would then want just x1::y1 to have unambiguous meaning on its own, which is impossible. As for x1:xN, it's unambiguous on its own. I thought one of the great advantages of R was that it could use different methods so that a new operator would not be needed. The colon operator would just

> From: Thomas Lumley > > On Sun, 30 Oct 2005, Jonathan Rougier wrote: > > > I'm not sure about this. Perhaps I am a dinosaur, but my feeling is > > that if people are writing functions in R that might be subject to > > simple operations like outer products, then they ought to be writing > > vectorised functions! > > I would agree. How about an

Dear Thomas, Right, thank you. Yes, I haven't looked at the source code (because I don't know C) but something like what you mention could well cause the kind of problems I am seeing: a loop being exectued one too few or one too many times. And yes, I think those quantities should be multiplied up by m*n to all become integers so we escape rounding error problems. David.

Version 3.18 of the survey package is now percolating through CRAN. Since the last announcement on this list, in February, the main additions are - standard errors for survival curves (both Kaplan-Meier and Cox model) - svyciprop() for confidence intervals on proportions, especially in small samples or near 0 or 1. - predictive margins by direct standardization, with marginpred() -

Version 3.18 of the survey package is now percolating through CRAN. Since the last announcement on this list, in February, the main additions are - standard errors for survival curves (both Kaplan-Meier and Cox model) - svyciprop() for confidence intervals on proportions, especially in small samples or near 0 or 1. - predictive margins by direct standardization, with marginpred() -

'surveyNG' version 0.3 is on CRAN. This package provides experimental features for survey analysis that may be incorporated in the survey package in the future. Currently there are facilities for analysis of complex surveys using (possibly large) data sets stored in a SQLite database. However, analysis facilities for these SQL-backed survey designs are rather more limited than in the

'surveyNG' version 0.3 is on CRAN. This package provides experimental features for survey analysis that may be incorporated in the survey package in the future. Currently there are facilities for analysis of complex surveys using (possibly large) data sets stored in a SQLite database. However, analysis facilities for these SQL-backed survey designs are rather more limited than in the

-------------------------------------------------- From: "Ahoussou Sylvie" <sylvie.ahoussou at antilles.inra.fr> Sent: Friday, September 12, 2008 9:48 AM To: "Thomas Lumley" <tlumley at u.washington.edu> Subject: Re: [R] Complex sampling survey _ Use of survey package > Thanks for your answer > > I think I made a mistake when I recopied the 5 first rows of

The following caused a hard-to-diagnose problem for a user of the survey package. Presumably this is a strange Unicode thing, but is there a convenient reference for how the collation order is determined? I am surprised that adding the same character to the end of two strings of the same length can change the sorting order. in en_US.utf8 locale > "1//"<"10/" [1]

--- On Fri, 6/11/09, tlumley at u.washington.edu <tlumley at u.washington.edu> wrote: > From: tlumley at u.washington.edu <tlumley at u.washington.edu> > Subject: Re: [Rd] A fix that for 'bquote' that may work? (PR#14031) > To: suharto_anggono at yahoo.com > Cc: r-devel at stat.math.ethz.ch, R-bugs at r-project.org > Date: Friday, 6 November, 2009, 11:42 PM >