Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 34948200BB7 for ; Wed, 26 Oct 2016 00:49:39 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 3350D160AFA; Tue, 25 Oct 2016 22:49:39 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 6CE56160AD8 for ; Wed, 26 Oct 2016 00:49:38 +0200 (CEST) Received: (qmail 92897 invoked by uid 500); 25 Oct 2016 22:49:37 -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 92882 invoked by uid 99); 25 Oct 2016 22:49:37 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 25 Oct 2016 22:49:37 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id AEC86C6D71 for ; Tue, 25 Oct 2016 22:49:36 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 0.748 X-Spam-Level: X-Spam-Status: No, score=0.748 tagged_above=-999 required=6.31 tests=[KAM_INFOUSMEBIZ=0.75, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id 7RXls9efrJrt for ; Tue, 25 Oct 2016 22:49:34 +0000 (UTC) Received: from brown.birch.relay.mailchannels.net (brown.birch.relay.mailchannels.net [23.83.209.23]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTPS id 76A7C5F1D5 for ; Tue, 25 Oct 2016 22:49:33 +0000 (UTC) X-Sender-Id: hostpapa|x-authuser|mail@berndporr.me.uk Received: from relay.mailchannels.net (localhost [127.0.0.1]) by relay.mailchannels.net (Postfix) with ESMTP id 0F073101A73 for ; Tue, 25 Oct 2016 22:49:26 +0000 (UTC) Received: from hp109.hostpapa.com (ip-10-229-2-62.us-west-2.compute.internal [10.229.2.62]) by relay.mailchannels.net (Postfix) with ESMTPA id 69DCA101DED for ; Tue, 25 Oct 2016 22:49:25 +0000 (UTC) X-Sender-Id: hostpapa|x-authuser|mail@berndporr.me.uk Received: from hp109.hostpapa.com (hp109.hostpapa.com [10.28.138.177]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384) by 0.0.0.0:2500 (trex/5.7.8); Tue, 25 Oct 2016 22:49:25 +0000 X-MC-Relay: Neutral X-MailChannels-SenderId: hostpapa|x-authuser|mail@berndporr.me.uk X-MailChannels-Auth-Id: hostpapa X-MC-Loop-Signature: 1477435765669:1094221711 X-MC-Ingress-Time: 1477435765668 Received: from host-92-27-239-9.static.as13285.net ([92.27.239.9]:65055 helo=[192.168.1.2]) by hp109.hostpapa.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.87) (envelope-from ) id 1bzAX4-003DVP-Ho for dev@commons.apache.org; Tue, 25 Oct 2016 23:49:23 +0100 Subject: Re: [complex] commons-complex module To: dev@commons.apache.org References: From: Bernd Porr Message-ID: Date: Tue, 25 Oct 2016 23:49:23 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.3.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-OutGoing-Spam-Status: No, score=-0.2 X-AuthUser: mail@berndporr.me.uk archived-at: Tue, 25 Oct 2016 22:49:39 -0000 Hi all, I agree that 'filter' is slightly problematic but I'd say because it's been used in different contexts and often misleading. However, I cannot think of a better word. That also depends where we place 2D image processing. They are also called filters. For IIR , Kalman(and possibly FIR) filters these are causal digital filters as they essentially behave as an analogue circuit in a digital form. For the casual (!) user of filters they'd probably just look for a filter... /Bernd On 25-Oct-16 23:00, Gary Gregory wrote: > On Tue, Oct 25, 2016 at 12:07 PM, Eric Barnhill > wrote: > >> On Tue, Oct 25, 2016 at 7:32 PM, Gary Gregory >> wrote: >> >>> I am against this constant spinning out. >>> >>> Gary >>> >>> >> The proposed commons-filter is not a spin out. There was one filter in math >> and it didn't belong there. Now we have at least couple of people around >> who know signal processing and would like to make a commons-filter package. >> Virtually none of which is coming from commons-math except dependencies. >> Does such a package suit commons? I think so. Filtering is needed from >> image processing to statistics. Others can vote no if they disagree. >> >> Complex was in math too. Did it belong there? In C++ or Python, complex is >> just another data type, like String. Its placement in math was not >> straightforward. A self contained component to handle complex data types >> seems more sensible to me than having it in Math. In any case Gilles is >> making me a branch to populate, so that I can propose this component later, >> IIUC. >> > It sounds like you can create your new component on top of math4, correct? > You do not need anything else? Aside from a better component name IMO. > "filter" is way to generic for me. > > Gary > >> >> Eric >> > > -- http://www.eigenproductions.co.uk http://www.linux-usb-daq.co.uk http://www.berndporr.me.uk http://www.imdb.com/name/nm3293421/ +44 (0)7840 340069 --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org For additional commands, e-mail: dev-help@commons.apache.org