Re: Question: Can LowLevelCallable functions be beneficial to scipy.optimize performance?
Andrew Nelson <[email protected]> Mon, 19 Feb 2024 19:35:22 +1100
| Newsgroups | gmane.comp.python.scientific.devel |
|---|---|
| Message-ID | <CAAbtOZd+Megp=oOR+Axa0nn0ho_33tapB=J8Z5G-k3L=3_Tf9A@mail.gmail.com> |
--===============5755739283593313932== Content-Type: multipart/alternative; boundary="0000000000001ee94d0611b7fa9c" --0000000000001ee94d0611b7fa9c Content-Type: text/plain; charset="UTF-8" On Mon, Feb 19, 2024, 19:28 Gabriel Fougeron <[email protected]> wrote: > > Do you think it would be possible to develop your examples to the point > where it's an easier tutorial for us. > > On the other hand, dealing with the LowLevelCallable in your own code is a > mess! Especially (like I did) if you want to somewhat abstract the return > type of the function (for the purposes of integrating scalar and vector > functions for instance). The code I came up with is much too verbose and > cluttered to my liking. > I was talking about using a lowlevelcallable from Python code, much like what your example shows. > AND there is the issue that I raised a few months ago which attracted > little attention. Cf https://github.com/scipy/scipy/issues/19148 > Until this issue has been addressed, users won't be able to use > LowLevelCallable without my dirty workaround anyways, so having a nice > tutorial is counter productive. > This being said, I would be thrilled to contribute with a nice tutorial > once this roadblock has been lifted. > > I think that's ok, but I don't know how to make those files available. --0000000000001ee94d0611b7fa9c Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div dir=3D"auto"><div><br><br><div class=3D"gmail_quote"><div dir=3D"ltr" = class=3D"gmail_attr">On Mon, Feb 19, 2024, 19:28 Gabriel Fougeron <<a hr= ef=3D"mailto:[email protected]">[email protected]</a>&g= t; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 = .8ex;border-left:1px #ccc solid;padding-left:1ex">> Do you think it woul= d be possible to develop your examples to the point<br> where it's an easier tutorial for us.<br> <br> On the other hand, dealing with the LowLevelCallable in your own code is a = mess! Especially (like I did) if you want to somewhat abstract the return t= ype of the function (for the purposes of integrating scalar and vector func= tions for instance). The code I came up with is much too verbose and clutte= red to my liking.<br></blockquote></div></div><div dir=3D"auto"><br></div><= div dir=3D"auto">I was talking about using a lowlevelcallable from Python c= ode, much like what your example shows.</div><div dir=3D"auto"><br></div><d= iv dir=3D"auto"><br></div><div dir=3D"auto"><div class=3D"gmail_quote"><blo= ckquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #c= cc solid;padding-left:1ex"><br> AND there is the issue that I raised a few months ago which attracted littl= e attention. Cf <a href=3D"https://github.com/scipy/scipy/issues/19148" rel= =3D"noreferrer noreferrer" target=3D"_blank">https://github.com/scipy/scipy= /issues/19148</a><br> Until this issue has been addressed, users won't be able to use LowLeve= lCallable without my dirty workaround anyways, so having a nice tutorial is= counter productive.<br> This being said, I would be thrilled to contribute with a nice tutorial onc= e this roadblock has been lifted.<br><br> </blockquote><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;b= order-left:1px #ccc solid;padding-left:1ex">I think that's ok, but I do= n't know how to make those files available.</blockquote></div></div></d= iv> --0000000000001ee94d0611b7fa9c-- --===============5755739283593313932== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ SciPy-Dev mailing list -- [email protected] To unsubscribe send an email to [email protected] https://mail.python.org/mailman3/lists/scipy-dev.python.org/ Member address: [email protected] --===============5755739283593313932==--