similar to: lapply - value changes as parameters to function?

Hi, I have a question about logistic regression in R. Suppose I have a small list of proteins P1, P2, P3 that predict a two-class target T, say cancer/noncancer. Lets further say I know that I can build a simple logistic regression model in R model <- glm(T ~ ., data=d.f(Y), family=binomial) (Y is the dataset of the Proteins). This works fine. T is a factored vector with levels cancer,

Hi, My results are getting out of order after I do the following command: count = result.inject({}) { |hsh, row| hsh[row[''name'']] = row[''count''].to_i; hsh } Why? Here are more specifics: My complete method is this (based off of acts_as_taggable code - not'' DHHs, but the original one): def self.sql_to_count_plays(lookback) sql =

Hi, I have a CentOS 5.0 LAMP server, and I need to install the php-yaz module to implement the Z39.50 protocol (which handles data exchange for public libraries). I've already done this with Debian (a one-liner: apt-get install php-yaz) and also on Slackware (more complicated: compile Yaz, rebuild PHP). Has anyone here ever done this on CentOS? What would be the most orthodox method to

> - set sampling rate to 8 kHz (at least for now) > - make sure the far end signal in the playback signal is always a bit in > advance (never late) compared to the mic signal. > - Set the tail length to something around 100 ms. > > Also, if you're using two different soundcards (as I understand) for the > playback and the capture, you're *never* going to get echo

Hello, I''m currently trying to understand some problems I had in the past with mixing look-back with blktap(2) for HV and PV domains. I''m stuck reading the source code, so I''d like to get some help from the list. Interrupt me if I got something fundamentally wrong in my understanding so far: 1. With pure-HV the domU gets an emulated IDE (or whatever) disk. The

Hi, Our public library management software (PMB) runs on Apache/PHP/MySQL. It requires some additional PHP modules to run correctly, namely: 1) php-gd 2) php-yaz 3) php-xslt I've googled and fiddled around quite a bit, and come to the following conclusions: 1) php-gd can be installed from extra repos (rpmforge IIRC), so this one's no problem. 2) To install php-yaz, I have to

Hello, include <iostream>#include <string>#include <xapian.h>struct document{ std::string title; std::string content; std::string url;}; void indexData(document d) { try { Xapian::WritableDatabase db("/Users/ramesh/Desktop/xapian", Xapian::DB_CREATE_OR_OPEN); Xapian::TermGenerator indexer; Xapian::Stem

Hello, include <iostream>#include <string>#include <xapian.h>struct document{ std::string title; std::string content; std::string url;}; void indexData(document d) { try { Xapian::WritableDatabase db("/Users/ramesh/Desktop/xapian", Xapian::DB_CREATE_OR_OPEN); Xapian::TermGenerator indexer; Xapian::Stem

https://bugzilla.samba.org/show_bug.cgi?id=1818 Summary: Rsyncd refuses connection if reverse mapping fails Product: rsync Version: 2.5.7 Platform: Other OS/Version: Linux Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned@samba.org ReportedBy: heikki@indexdata.dk

Hello all. Apologies... I was a little too eager in my earlier annoucement about the Indexed Search Engine for Rails apps. The DB migration file contained an error that had to be worked around. I''ve fixed that, added more (and clearer) documentation, and a sample application. You can find most everything you want to know about Indexed Search Engine here:

> I did a bit more testing, and ended up creating a set of testsamples, as > follows: > > ideal.pcm => me saying "This is what I'd like to hear" > junk.pcm => me saying "With a bit of luck, this is gone" > mixdown.pcm => ideal.pcm, with junk.pcm started 7 ms later and 3 dB lower. The problem with that is that it's nowhere near real

http://bugzilla.mindrot.org/show_bug.cgi?id=1049 Summary: Variable delay in password logins to fight dictionary attacks Product: Portable OpenSSH Version: 3.8.1p1 Platform: ix86 OS/Version: Linux Status: NEW Severity: enhancement Priority: P2 Component: sshd AssignedTo:

tl;dr in low data situations we don’t look at past information, and that increases the false positive regression rate. We should look at the possibly incorrect recent past runs to fix that. Motivation: LNT’s current regression detection system has false positive rate that is too high to make it useful. With test suites as large as the llvm “test-suite” a single report will show hundreds of

I'm trying to convert my current headphones and microphone chat application to support loudspeakers and microphone, and so I thought I'd give speex_echo_cancel() a try. Since my users quite frequently have other sound-producing applications running on their computer (such as winamp), I sample 'wave' recording device of the soundcard in addition to the microphone. I then call

I've been working on this the past few days and thought I would put it out there to see if anyone else has interest in it. It really has nothing to do with the Digium appliance, I've just been looking for some mass produced solid state hardware to run small branch offices off of for awhile now and I think I've finally landed on something I like. Basically I've taken an HP thin

Hi Chris and others! I totally support any work in this direction. In the current state LNT’s regression detection system is too noisy, which makes it almost impossible to use in some cases. If after each run a developer gets a dozen of ‘regressions’, none of which happens to be real, he/she won’t care about such reports after a while. We clearly need to filter out as much noise as we can - and