From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4448 invoked by alias); 10 Jan 2014 06:11:22 -0000 Mailing-List: contact gsl-discuss-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gsl-discuss-owner@sourceware.org Received: (qmail 4437 invoked by uid 89); 10 Jan 2014 06:11:21 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_LOW,SPF_SOFTFAIL autolearn=no version=3.3.2 X-HELO: mail-qc0-f178.google.com Received: from mail-qc0-f178.google.com (HELO mail-qc0-f178.google.com) (209.85.216.178) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES128-SHA encrypted) ESMTPS; Fri, 10 Jan 2014 06:11:20 +0000 Received: by mail-qc0-f178.google.com with SMTP id i17so3597164qcy.9 for ; Thu, 09 Jan 2014 22:11:18 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :subject:references:in-reply-to:content-type; bh=Cse9kvMfPwz+eCzvNG/FSwZ+rv8cvJIQ+zQmtxGjoUU=; b=JHZQmVFEiZgkR8JauNm28hXPo2U+4jEKN3ZsRYVepcc1TQ6ZSHjYoWLivPrDqEZviT /fArbpJsCnCsOXh3eRzKS1R519+FG0qVmX3+SGYUgi79d1ttK8GXOpH1TPpEFpTiSo1g At0UUEN7dRKiTqIrdLKfYr3c+IcOtypZE6F5UdFEWjKF+7L3FuJkx6NuYUbuWBY48Aof +KwxcCVBITaSTzscZnb/l3uRx4yzA3jdl1SXL6r0wBvdFvnf4sdNSQM5fOerIf9uMiGh vC47calJvB8hE0p381M/uFsyFlPjAWBjMYG6MSm9E2erv9k1/fFOgLf/paIpINPlPJ/P uAxA== X-Gm-Message-State: ALoCoQnadkOX6S+38jwhiVT4E2ToyRz9NTtWQQ91kD/323lGu7rGdjis+mSmtKKO0GqP1kUDLERq X-Received: by 10.224.124.1 with SMTP id s1mr3605501qar.79.1389334278229; Thu, 09 Jan 2014 22:11:18 -0800 (PST) Received: from [192.168.1.119] (c-174-49-133-13.hsd1.pa.comcast.net. [174.49.133.13]) by mx.google.com with ESMTPSA id j7sm10253781qas.13.2014.01.09.22.11.17 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 09 Jan 2014 22:11:17 -0800 (PST) Message-ID: <52CF8F04.60505@ellipsix.net> Date: Fri, 10 Jan 2014 06:11:00 -0000 From: David Zaslavsky User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: gsl-discuss@sourceware.org Subject: Re: interp2d discussion References: <520EB115.9070606@ellipsix.net> <52C708E1.6010601@colorado.edu> <52C9C114.1010303@ellipsix.net> <52CAE093.5060001@colorado.edu> In-Reply-To: <52CAE093.5060001@colorado.edu> Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="1iIW5vQahwE8vaSu4gBCWG8Mqg4u92Rw6" X-SW-Source: 2014-q1/txt/msg00007.txt.bz2 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --1iIW5vQahwE8vaSu4gBCWG8Mqg4u92Rw6 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-length: 2340 Hi Patrick, Sorry for the delayed response; I've been quite busy this week. On 01/06/2014 11:57 AM, Patrick Alken wrote: > On 01/05/2014 01:31 PM, David Zaslavsky wrote: >> On the indexing issue: interp2d treats the x index as the column >> coordinate and the y index as the row coordinate, so that xsize is the >> number of columns and ysize is the number of rows. This is done for >> compatibility with Cartesian coordinates: most people envision x as the >> horizontal coordinate and y as the vertical one. Given this >> interpretation, the current implementation of INDEX_2D does use >> row-major order. > > This makes sense, we can probably leave it the way it is, we'll just > need to make sure the documentation is very clear on how to construct > the z array so users aren't confused with the indexing. Sure, that would be a reasonable option, but I'd like to do a bit of research (i.e. ask a few more people for opinions) to see what solution will be the least confusing. After all, if there is a change to be made, this is the time to do it, not later after the code is incorporated into GSL. I think backward compatibility will not be too much of a problem because people will have to make other changes anyway to transition from the interp2d_* functions to the corresponding gsl_* functions. >> Also, I should mention that I don't consider interp2d to be >> feature-complete, nor am I in any particular rush to make it complete. >> There are some features I'm interested in adding, including additional >> interpolation schemes, more interpolation methods without boundary >> checks (for extrapolation), etc. How would this move affect my ability >> to continue to add features? > > It already has bilinear and bicubic implemented. This is more than > enough to make it useful to people so I think we can put it in now and > continue adding features. > > I saw from some comments that you used some code from ALGLIB - can we > assume you're using the GPL v2 version of ALGLIB? In that case there > shouldn't be any problem putting it in GSL under GPL v3. The code was adapted from ALGLIB by Thomas Beutlich, and I'm pretty sure he told me that he used the GPL v2 version. I'll double-check that, though. When I have some time I'll fork the GSL repository and work on adding the interp2d code in a new branch. :) David --1iIW5vQahwE8vaSu4gBCWG8Mqg4u92Rw6 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" Content-length: 295 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iF4EAREIAAYFAlLPjwQACgkQBoP+cm/XtnTXEQEAmthQkACvJimb4ofsyJv10pr3 Pp5ZEFmrSzbjKhishhAA/3W4YS3g4vWQLHqK7Q6Il/E2UGb7T7dlVCAwpyYjaCy6 =wHF2 -----END PGP SIGNATURE----- --1iIW5vQahwE8vaSu4gBCWG8Mqg4u92Rw6--