From user-return-27999-apmail-commons-user-archive=commons.apache.org@commons.apache.org Thu Dec 13 14:59:36 2012 Return-Path: X-Original-To: apmail-commons-user-archive@www.apache.org Delivered-To: apmail-commons-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id C07A1DB23 for ; Thu, 13 Dec 2012 14:59:36 +0000 (UTC) Received: (qmail 58758 invoked by uid 500); 13 Dec 2012 14:59:35 -0000 Delivered-To: apmail-commons-user-archive@commons.apache.org Received: (qmail 58620 invoked by uid 500); 13 Dec 2012 14:59:32 -0000 Mailing-List: contact user-help@commons.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Commons Users List" Delivered-To: mailing list user@commons.apache.org Received: (qmail 58601 invoked by uid 99); 13 Dec 2012 14:59:31 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 13 Dec 2012 14:59:31 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of ted.dunning@gmail.com designates 209.85.223.171 as permitted sender) Received: from [209.85.223.171] (HELO mail-ie0-f171.google.com) (209.85.223.171) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 13 Dec 2012 14:59:25 +0000 Received: by mail-ie0-f171.google.com with SMTP id 17so4142567iea.30 for ; Thu, 13 Dec 2012 06:59:04 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; bh=5QzqFJ5i8qBm6KJvr7TODY+Up18kFKJR5dmri1iatM8=; b=d/YEXtnSmrXpTf5o6gmDOcUK/Wf8UG4P2zYSNS5JkmnrBFkLJYFRQUXY+Ra5jaC/qC q69wRN1LNnC4ywycetCnrBoiY3AILSGMHAuj0Y/a9/muMekHoX1jP2RqGS85Yybscbw9 jhINR1evjNGTl1EMb5A3BTmJsdGZtYT7et7IuRzHvMvN9vg5v4Ee+TyW+AQA1WVls4gG TLRWaXraHwMnRHfYEiu813DyKm0SuD8v2K9Dozf5b0YZ0pSr3hJb/1jsnnqJC47oGPwJ OZd6ElpWJNGLhuo3P4jKz3O8DV2tooz45m13I5e1xm7fmoM9hUsrThyTP59eV28Qux1h DOLg== Received: by 10.50.6.169 with SMTP id c9mr1874479iga.24.1355410744793; Thu, 13 Dec 2012 06:59:04 -0800 (PST) MIME-Version: 1.0 Received: by 10.64.97.106 with HTTP; Thu, 13 Dec 2012 06:58:34 -0800 (PST) In-Reply-To: <50C9EC03.4040207@fu-berlin.de> References: <50C9EC03.4040207@fu-berlin.de> From: Ted Dunning Date: Thu, 13 Dec 2012 06:58:34 -0800 Message-ID: Subject: Re: [math] correlation analysis with NaNs To: Commons Users List Content-Type: multipart/alternative; boundary=e89a8f646717f7d9c404d0bd2734 X-Virus-Checked: Checked by ClamAV on apache.org --e89a8f646717f7d9c404d0bd2734 Content-Type: text/plain; charset=UTF-8 This is a nice way to allow various conventions. Sometimes -1 might be the right value. Other times a more principled value like NaN might be reasonable. My proposal would be that for every algorithm that is able to handle >> missing data, we provide an argument (to constructors) that specifies the >> "double" value that represents a missing value. >> > --e89a8f646717f7d9c404d0bd2734--