Return-Path: Delivered-To: apmail-commons-dev-archive@www.apache.org Received: (qmail 49456 invoked from network); 12 Dec 2009 19:17:58 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 12 Dec 2009 19:17:58 -0000 Received: (qmail 47304 invoked by uid 500); 12 Dec 2009 19:17:57 -0000 Delivered-To: apmail-commons-dev-archive@commons.apache.org Received: (qmail 47151 invoked by uid 500); 12 Dec 2009 19:17:57 -0000 Mailing-List: contact dev-help@commons.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Commons Developers List" Delivered-To: mailing list dev@commons.apache.org Received: (qmail 47140 invoked by uid 99); 12 Dec 2009 19:17:57 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 12 Dec 2009 19:17:57 +0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of ted.dunning@gmail.com designates 209.85.216.195 as permitted sender) Received: from [209.85.216.195] (HELO mail-px0-f195.google.com) (209.85.216.195) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 12 Dec 2009 19:17:48 +0000 Received: by pxi33 with SMTP id 33so1349783pxi.10 for ; Sat, 12 Dec 2009 11:17:27 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :from:date:message-id:subject:to:content-type; bh=1FNgEYlW7Fy+CtUhXHRvllABd6/GPWs0zNFa2GRbwD0=; b=WFKK7iap9qmc7m7aXoneebiKMEZkqrBWSdR/nhQhkyYLhUrg4yT41OtqZFeAaTRyVE Y20DRGUUy2s2E/xPUaRw6Gw99Aq0mZmpwT4VADX+w+2ayMSrc0douS6DV2PK/TBfyv7z 99Z1tFBNQqjP+2QKSgAGa6HgFylpIRzezTCog= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; b=B/Q6V0a1SAO/mowIy7Wt00rnsCnUq3TjihWQGiInW5NHSJsZyLG/Yt9tYxe1gPbEGF Y4tH+u1Ea5/QVKy0nNSUFAKUvnZF1FgQebO55CehzpKYHLT7WRvjhFQRynapvQXwOoFU y3BfewKSR7cc/QJWk5k4iwyHM2QFydK/MPato= MIME-Version: 1.0 Received: by 10.114.189.40 with SMTP id m40mr1800266waf.228.1260645447057; Sat, 12 Dec 2009 11:17:27 -0800 (PST) In-Reply-To: <4B23C64C.3040605@yahoo.de> References: <61b5d9410912080518p68708d9fie8405ca274029947@mail.gmail.com> <61b5d9410912080619k76b70dd1uc04a9fb3492402f2@mail.gmail.com> <4B1FF0F4.1000505@free.fr> <61b5d9410912091109t40ff7b6cu6089c5dd0198990e@mail.gmail.com> <4b124c310912091158r7e4aef26u4fca47a585457df4@mail.gmail.com> <4B23C64C.3040605@yahoo.de> From: Ted Dunning Date: Sat, 12 Dec 2009 11:17:07 -0800 Message-ID: Subject: Re: [math] getting changes included into commons-math (was Re: Home for the colt fork) To: Commons Developers List Content-Type: multipart/alternative; boundary=0016e64ccdde0f428b047a8ce4c1 X-Virus-Checked: Checked by ClamAV on apache.org --0016e64ccdde0f428b047a8ce4c1 Content-Type: text/plain; charset=UTF-8 MATH-312, 314, 316 and 317 were the first round. Some of the necessary changes included: - sparse iterators for sparse vectors - view semantics for sub-matrix and sub-vectors - additional sparse vector types for specialized applications - introduction of an unbounded sparse matrix/vector that simply remembers the highest bound set - introduction of abstract classes to allow off the cuff inner implementations of virtual vectors - introduction of additional decomposition classes - introduction of row and column label abstraction for matrices and vectors - higher performance implementations The 5 issues that Jake filed were mostly address the first point. That stalled out when he hit resistance to change. Since then we have adopted Colt as our matrix/linear algebra/collections implementation and we don't really need any changes to MATH. On Sat, Dec 12, 2009 at 8:35 AM, J.Pietschmann wrote: > On 09.12.2009 20:58, Jake Mannix wrote: > >> The commons-math linear APIs have been described as effectively locked >> until 3.0, due to back-compat requirements. >> > > Can you give a short summary of the API changes which are necessary > to incorporate and use the functionality you need? Some functionality > I've seen mentioned here could probably be pressed in the existing > API, but I may have missed some details. > > J.Pietschmann > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org > For additional commands, e-mail: dev-help@commons.apache.org > > -- Ted Dunning, CTO DeepDyve --0016e64ccdde0f428b047a8ce4c1--