search for: nondupl

Hi, Has anyone been able to figure out how to print all duplicated observations? I have a dataset, with patients ID, and other lab records. Some patients have multiple lab records, but 'duplicated' ID will only show me the duplicates, not the original observation. How can I print both the original one and the duplicates? Thanks

...(1|id) + (1|visn2) f <- MPR100 ~ TIME + NHB + HISPANIC + OTHER + (1|ID) boot.rem <- function(data, id, pct, time, formula, reps, vars) { ## Order the observations accroding to increasing ID my.df2 <- vcohort[order(data$ID, decreasing=FALSE),] ## Create a vector of nonduplicating IDs unique.id <- my.df2[!duplicated(my.df2[,"ID"]),"ID"] ## Determine the sample size as a percentage of ## the population sz <- length(unique.id)*(pct/100) ## Create a matrix of NAs with ROWS equal to the number ## of REPS and the number of col...

I noticed the following today --- str() seems to remove any extra class information added to an environment. > e <- new.env() > class(e) [1] "environment" > class(e) <- c("foo", class(e)) > class(e) [1] "foo" "environment" > str(e) Classes 'foo', 'environment' length 0 <environment> > class(e) [1]

I had high hopes of significant performance gains using zfs diff in Solaris 11 compared to my home-brew stat based version in Solaris 10. However the results I have seen so far have been disappointing. Testing on a reasonably sized filesystem (4TB), a diff that listed 41k changes took 77 minutes. I haven''t tried my old tool, but I would expect the same diff to take a couple of

On Fri, Jul 29, 2005 at 10:08:13AM +0100, james wrote: > SVN root: svn://svn.xapian.org/xapian > Changes by: james > Revision: 6355 > Date: 2005-07-29 10:08:13 +0100 (Fri, 29 Jul 2005) > > Log message (6 lines): > omindex.cc: add --preserve-nonduplicates / -p option to not delete any > documents that aren't updated, in replace duplicates mode (so that > multiple runs of omindex on different subsites don't stomp on each > other). This fix seems to be avoiding the real issue, so it's less than ideal I feel. Looking at the...

Hi. I am writing a python equivalent of omindex (we are using scriptindex currently - but I wanted to use omindex instead, and extend it to work with our internal file format.. BUT did not want to compile code if possible... so anyway). I have tried to keep the code as close to possible to the omindex native code, but am facing a bit of confusion: what exactly is the reason for omindex to take