Menu
▾
▴
matlisp-users
|
From: Michael A. K. <ma...@ll...> - 2002-06-21 18:20:16
|
> Instead of an array, I've decided to just do (push x seq) and then > (nreverse seq) at the end. This is quite fast for me. Ray, Yes...this worked faster for me is well. I've included it, w/ obvious mods, in my local working src copy. tnx for the quick response mike ************************************************** Dr Michael A. Koerber Micro$oft Free Zone MIT/Lincoln Laboratory ma...@ll... |
|
From: Michael A. K. <ma...@ll...> - 2002-10-29 17:00:05
|
> If R\t means R^(-1)*t, the (m/ t r) will do that. However, I think > that's probably rather expensive because it probably will use Gaussian > elimination to solve this set of equations. Some other special > routine from LAPACK should probably be used. (m/ A B) uses the LU decomposition routines. Not also the recent addition made (GETRS! ... ) uses LU. mike |
|
From: <ma...@ll...> - 2003-10-15 15:12:52
|
> This is acceptable to me. However, I think we need to think about > adding a script or something for the user to run to do the necessary > magic to get him into matlisp. We may also want to create a > matlisp.core, which I don't think currently happens. But I tend not > to save cores and instead load up the individual fasls. But matlisp > is big so loading these is a bit slow.... Saving the Matlisp core (as well as the sample Matlisp startup script) is, IMHO, required at least as a user selectable option. If changes are to be made to the make file, having a "make intall" would be nice. mike ************************************************** Dr Michael A. Koerber Micro$oft Free Zone MIT/Lincoln Laboratory |
|
From: Raymond T. <to...@rt...> - 2003-10-28 13:57:39
|
>>>>> "Michael" == mak <ma...@ll...> writes:
>> This is acceptable to me. However, I think we need to think about
>> adding a script or something for the user to run to do the necessary
>> magic to get him into matlisp. We may also want to create a
>> matlisp.core, which I don't think currently happens. But I tend not
>> to save cores and instead load up the individual fasls. But matlisp
>> is big so loading these is a bit slow....
Michael> Saving the Matlisp core (as well as the sample Matlisp startup script)
Michael> is, IMHO, required at least as a user selectable option. If changes
Michael> are to be made to the make file, having a "make intall" would be
Michael> nice.
FWIW, I have this working in my personal tree. "make" will just make
the matlisp.core. I think it should port to ACL, but I don't have ACL
to test it, so someone else will have to do that.
I don't yet have install done, but that should be straight-forward to
do.
I'll probably check this in some time soon.
Ray
|
|
From: <ma...@ll...> - 2003-10-15 19:30:27
|
> I think M+ and friends are fine because they're methods that take 2 > args. If matlisp:+ were used instead, it would break peoples' > expectation of being able to give multiple arguments. > > Adding such a macro to matlisp would be fine with me, but then we'd > get more complaints about this in addition to REAL. :-) I agree that M+ etc are fine. Although I frequently need a multiple-argument and multiple-type version. e.g., (+ MATLISP-REAL-MATRIX ARRAY-COMPLEX-2 SCALAR ARRAY-SINGLE-FLOAT-2) This might be a future enhancement for MATLISP. I currently define H+, H-, H*, H/ etc as Hadamard varients of each operation and keep adding methods as I need them for my work. mike |
|
From: <ma...@ll...> - 2003-10-28 16:08:23
|
Ray, > Ok, :matrix and :m are no longer nicknames for the matlisp package. Ouch! The removal of :M breaks 99% of my code. If this is necessary for the rest of the users, I'll make changes to my code (the script to update my code should be pretty simple). Else, I'd just as soon :M stay around. tnx mike ************************************************** Dr Michael A. Koerber Micro$oft Free Zone MIT/Lincoln Laboratory |
|
From: Raymond T. <to...@rt...> - 2003-10-28 16:06:55
|
>>>>> "Michael" == mak <ma...@ll...> writes:
Michael> Ray,
>> Ok, :matrix and :m are no longer nicknames for the matlisp package.
Michael> Ouch! The removal of :M breaks 99% of my code. If this is necessary for
Michael> the rest of the users, I'll make changes to my code (the script to update
Michael> my code should be pretty simple). Else, I'd just as soon :M stay around.
Sorry! No one had said anything, but perhaps I didn't give enough
time.
I'm not sure what to do. I think it's bad that matlisp defines such a
short package nickname, along with the rather generic :matrix
nickname.
We could do what Kent Pitman suggested on c.l.l a while back and
change the matlisp package to be net.sourceforge.matlisp or
net.sf.matlisp. But I think matlisp is sufficiently unique that we
don't have to do that.
Would it be acceptable to you if you just added
(rename-package "MATLISP" "MATLISP" "M")
in some appropriate startup file of yours? This will re-establish the
M nickname.
Ray
|
|
From: <ma...@ll...> - 2003-10-28 18:16:00
|
> Sorry! No one had said anything, but perhaps I didn't give enough > time. I may have not been following the thread carefully enough. I didn't pickup on the :M proposed change. > We could do what Kent Pitman suggested on c.l.l a while back and > change the matlisp package to be net.sourceforge.matlisp or > net.sf.matlisp. But I think matlisp is sufficiently unique that we > don't have to do that. It seems to me that :MATLISP is sufficient. > Would it be acceptable to you if you just added > > (rename-package "MATLISP" "MATLISP" "M") this works fine for me. tnx mike |
|
From: Raymond T. <to...@rt...> - 2002-06-21 18:28:27
|
>>>>> "Michael" == Michael A Koerber <ma...@ll...> writes:
>> Instead of an array, I've decided to just do (push x seq) and then
>> (nreverse seq) at the end. This is quite fast for me.
Michael> Ray,
Michael> Yes...this worked faster for me is well. I've included it, w/ obvious mods,
Michael> in my local working src copy.
Michael> tnx for the quick response
Thank you for finding the bug, and testing out a new solution!
I'd check it into CVS but I can't seem to access it today.
Sourceforge problems, I guess.
I'll do it soon.
Ray
|
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X