March 2013 - gsll-devel - mailman3.common-lisp.net

[GSLL-devel] Fixing up make-grid-data for clisp (was making copy-to working in clisp+grid: fix to element-type)
by Mirko Vukovic 26 Dec '13

26 Dec '13

This is a follow up on my posted fix to copy-to. For some reason this has triggered another error. I do not understand how that other error is triggered. The error and the fix are discussed at the bottom of the email On Fri, Jan 4, 2013 at 10:39 AM, Mirko Vukovic <mirko.vukovic(a)gmail.com>wrote: > The following works in sbcl+grid: > > (copy-to (make-array 2 :element-type 'double-float :initial-contents > '(1.0d0 2.0d0)) 'grid:foreign-array) > > But it does not work in clisp+grid. > > The root cause lies in the function grid/array.lisp/element-type. It uses > `(array-element-type grid)'. > > But this can present a problem. Quoting hyperspec: > > (Because of *array* <http://26_glo_a.htm#array> *upgrading*, this *type > specifier* <http://26_glo_t.htm#type_specifier> can in some cases denote > a *supertype* <http://26_glo_s.htm#supertype> of the *expressed array > element type* <http://26_glo_e.htm#expressed_array_element_type> of the * > array*.) > > In CLISP, array-element-type returns `T' when passed #(1d0 2d0) > > It returns T even when passed a simple array: > > (array-element-type (make-array 2 :element-type 'double-float > :initial-contents > '(1.0d0 2.0d0) > :adjustable nil > :fill-pointer nil > :displaced-to nil) ) > > The proposed fix is > > (defmethod element-type ((grid array)) > (type-of (row-major-aref grid 0)) > #+skip(array-element-type grid)) > > Now copy-to works in clisp as well. > > Mirko > > > After finishing this, I recompiled afresh, and got another error that I traced to make-grid-data and make-array In clisp, make-array will return an array of NIL's even if the element-type is specified as double float. In SBCL make-array will return an array filled with 1d0. I had to add some clisp specific code to make-grid-data in order for it to initialize properly. First, a helper function: (defun default-element (element-type) "Return a default element depending on element-type " (let ((a-list '((double-float . 1d0) (symbol . T)))) (let ((match (cdr (assoc element-type a-list)))) (assert match () "Default element type undefined for element-type ~a" element-type) match))) And second, a bit of set-up code in make-grid-data. I broke apart the (let* statement to provide an explicit initial element if it has not been specified already: (defmethod make-grid-data ((type (eql 'array)) dimensions rest-spec &key (initial-element nil initial-element-p) (initial-contents nil initial-contents-p)) (let ((element-type (top-spec-type rest-spec))) #+clisp (unless (or initial-element-p initial-contents-p) (setf initial-element (default-element element-type) initial-element-p t)) (let ((array ... UNCHANGED Summary: To fix to copy-to, I modified (defmethod element-type ((grid array)) For some unknown reason, that triggered an error in the array initialization routine. To fix that, I had to add code to make-grid-data, so that it fills double-float arrays with 0d0 instead of NIL's I will continue using this code to see if there are additional problems. BTW, I realize that CLISP is not a preferred platform for speedy computation, but that is what I use on Windows, until SBCL gets officially ported to it. And in addition, it is a nice cross-check on portability. Mirko

2 2

[GSLL-devel] making copy-to working in clisp+grid: fix to element-type
by Mirko Vukovic 26 Dec '13

26 Dec '13

The following works in sbcl+grid: (copy-to (make-array 2 :element-type 'double-float :initial-contents '(1.0d0 2.0d0)) 'grid:foreign-array) But it does not work in clisp+grid. The root cause lies in the function grid/array.lisp/element-type. It uses `(array-element-type grid)'. But this can present a problem. Quoting hyperspec: (Because of *array* <26_glo_a.htm#array> *upgrading*, this *type specifier*<26_glo_t.htm#type_specifier>can in some cases denote a *supertype* <26_glo_s.htm#supertype> of the *expressed array element type*<26_glo_e.htm#expressed_array_element_type>of the *array*.) In CLISP, array-element-type returns `T' when passed #(1d0 2d0) It returns T even when passed a simple array: (array-element-type (make-array 2 :element-type 'double-float :initial-contents '(1.0d0 2.0d0) :adjustable nil :fill-pointer nil :displaced-to nil) ) The proposed fix is (defmethod element-type ((grid array)) (type-of (row-major-aref grid 0)) #+skip(array-element-type grid)) Now copy-to works in clisp as well. Mirko

2 1

[GSLL-devel] CFFI release 0.11.0
by Liam Healy 03 Mar '13

03 Mar '13

CFFI 0.11.0 was released last week. This includes cffi-libffi, which makes FSBV obsolete. The new versions of Antik and GSLL now use cffi-libffi instead of FSBV. For most users of these systems, this is an internal detail and unimportant. However, for the past 6 months at least, I have been using and updating these versions and not the FSBV version. So, with these branches merged into the master branch, a number of patches and fixes have made there way into the master branch. I expect in the March update to quicklisp, all these changes will be in the new dist. Waiting for CFFI to be finalized blocked a number of projects. One is to split up Antik into different systems instead of making one system that loads everything (grid, physical quantities, etc.). Another is dataflow definitions (and coordination with org-mode) that I am just starting on. In GSLL, I've started to look at the definition of physical constants. I don't know when I'll have time to work on these or when they'll be complete, but I'll update when I have something. Liam

1 0

Re: [GSLL-devel] Matlisp
by Akshay Srinivasan 01 Mar '13

01 Mar '13

At Thu, 28 Feb 2013 07:00:27 +0100, A.J. Rossini wrote: > > Regarding the auto-gen'd BLAS and LAPACK FFI stuff, it's cl-blapack > you want to look at. Rif did a pretty complete job of writing that. > I'd look at that for the CFFI stubs, though it would be nice to have > the alpha/beta status Fortran-CFFI stuff moved out of an experimental > state (I'm as guilty as everyone else for that problem). > > There's a lisp-matrix google group that should have some of Mark H / > Rif / Tamas' earlier discussions from the late 2000s that should be > reviewed. Did you review that list, Akshay? I think I've looked at the webpage that was put up by Mark on Berkeley's site. I think the tensor branch sort of satisfies all of them (except perhaps for the LAPACK bits?). Please though take a look at the code. Akshay > > > best, > -tony > > blindglobe(a)gmail.com > Muttenz, Switzerland. > "Commit early,commit often, and commit in a repository from which we > can easily roll-back your mistakes" (AJR, 4Jan05). > > Drink Coffee: Do stupid things faster with more energy!

1 0

Re: [GSLL-devel] Matlisp
by Liam Healy 01 Mar '13

01 Mar '13

Hi Akshay, Thank you for your work and your email. I think a lot of people have had very similar thoughts to yours, and have started down the road meeting the needs of users they've identified. There are a lot of good and partially overlapping ideas within this loosely organized group of people. There was a similar discussion started in the context of common lisp stats (which I'm not a member of) a few months ago. Where I was participating, I cc'ed the antik-devel mailing list; see for example http://lists.common-lisp.net/pipermail/antik-devel/2012q4/000019.html and the archives in general http://lists.common-lisp.net/pipermail/antik-devel/2012q4/thread.html with the subject "numerical lisp". My feeling is that we need to break the desired functions into relatively narrow, compatible libraries. I started Antik as a split out of GSLL to handle "grids" (generalized arrays) to start down that road. It needs to be split up further, because it now includes other things such as calculations with physical dimensions. I've started that further split, but haven't done any work on it recently. I am interested in the work you've done; it's been a while since I looked at Matlisp. At the time, it did not meet my needs, but it seems you have done significant work on it and has a lot of potential to be part of the compatible family of libraries as I've described. I think a good first step is to identify the different areas (for example, generalized arrays as I've indicated, or statistics functions) and canvas the current state of software for features and capabilities. I've added Tamas Papp and Mirko Vukovic onto this email because they've been very active in thinking about these things. Also I've added the Antik and GSLL mailing lists for good measure. Liam On Wed, Feb 27, 2013 at 1:04 AM, Akshay Srinivasan <akshaysrinivasan(a)gmail.com> wrote: > Hello All, > I'm sort of the active developer of Matlisp these days (mostly whilst procrastinating > from doing more "academic" work). I know all of you have created your independent system for > scientific computing on Common Lisp, and it is really a pity that all of them (including the > old Matlisp) are not particularly usable when compared with something like SciPy or Matlab even; > more so since Lisp is so much nicer a language. > I think the version of Matlisp I'm developing has a lot of promise, and is taking a very > good shape (atleast I'd like to think so). I'm personally trying to use it for my work in Control > theory and such; but it's still not something which is particularly usable yet. The improvements over > the old version of Matlisp are: > - Use of a hacky static object system, so that functions can be generated for any user-defined "field". > There is some code demonstrating the use of Maxima to work with "symbolic-tensors", there isn't > code for integer matrices yet, but getting this to work is fairly trivial. > - The tensor (multi-array) structures can now be sliced inplace very easily like SciPy. > - Automatic fortran callback generation (see dlsode.lisp). There are plans to extend this to C, so > that we can make use of GSL. > - Lisp implementations of BLAS functions, and support for seamlessly switching between the Lisp and > Fortran versions of these routines. The lisp version of GEMM (and others) is nearly as fast as the > F77 reference BLAS one, on SBCL. > - The FFI has moved to CFFI, if you haven't noticed that yet; builds on CCL and CMUCL. > The basic structure of BLAS is out there, but the LAPACK wrappers are missing. However I do think that > the general structure of the code is in place. > > I just wanted to throw out the idea into the open, about the feasibility of merging all your > projects into Matlisp (and calling it by some other name, if that is an issue) ? Would any of you > be willing to take the time to go through my code and merge yours in ? I'm writing to you now > before I take time and polish things, because then there'd be little room to make architectural > changes later on. The code is here if you'd like to give it a try: > git://matlisp.git.sourceforge.net/gitroot/matlisp/matlisp tensor > or if you just want to browse the code: > https://github.com/enupten/matlisp > You may want to look at the (ugly) code in tests/ folder to get an idea about the code behaviour. > You'd also want to work in #:matlisp package (despite what the herald says). > > Getting the maxima bits to work is kind of tricky, but you don't really need it for numerical routines > to work. > > Akshay

2 1