[Numpy-discussion] Re: Welcome Joren Hammudoglu to the NumPy Maintainers Team
Welcome Joren and tx for your contribs! Il giorno lun 19 ago 2024 alle ore 15:14 Warren Weckesser < warren.weckes...@gmail.com> ha scritto: > On Mon, Aug 19, 2024 at 6:45 AM Sebastian Berg > wrote: > > > > Hi all, > > > > please join me in welcoming Joren (https://github.com/jorenham) to the > > NumPy maintainers team. > > > > Welcome Joren! > > Warren > > > Joren has done a lot of work recently contributing, reviewing, and > > maintaining typing related improvements to NumPy. > > We are looking forward to see new momentum to improve NumPy typing. > > > > Thanks for all the contributions! > > > > Cheers, > > > > Sebastian > > > > ___ > > NumPy-Discussion mailing list -- numpy-discussion@python.org > > To unsubscribe send an email to numpy-discussion-le...@python.org > > https://mail.python.org/mailman3/lists/numpy-discussion.python.org/ > > Member address: warren.weckes...@gmail.com > ___ > NumPy-Discussion mailing list -- numpy-discussion@python.org > To unsubscribe send an email to numpy-discussion-le...@python.org > https://mail.python.org/mailman3/lists/numpy-discussion.python.org/ > Member address: renato.fab...@gmail.com > -- Renato Fabbri -- ___ NumPy-Discussion mailing list -- numpy-discussion@python.org To unsubscribe send an email to numpy-discussion-le...@python.org https://mail.python.org/mailman3/lists/numpy-discussion.python.org/ Member address: arch...@mail-archive.com
Re: [Numpy-discussion] Fwd: [numfocus] Grants up to $3k available to NumFOCUS projects (sponsored & affiliated)
maybe OT, but is has become recurrent to me for already some years to make a very simple module for obtaining arrays related to musical elements. All here: https://github.com/ttm/dissertacao scripts/ have Python/Numpy has implementions of the musical elements. dissertacaoCorrigida.pdf holds a thorough description of the framework. I idealize it as a module inside Numpy but I understand it might be reasonable to do it as a Scipy kit. I handed my doctorate a few days ago and might be willing to put some time into this. PS. long time no post. Hello! On Mon, Apr 3, 2017 at 8:28 AM, Julian Taylor wrote: > On 31.03.2017 16:07, Julian Taylor wrote: > > On 31.03.2017 15:51, Nathaniel Smith wrote: > >> On Mar 31, 2017 1:15 AM, "Ralf Gommers" >> <mailto:ralf.gomm...@gmail.com>> wrote: > >> > >> > >> > >> On Mon, Mar 27, 2017 at 11:42 PM, Ralf Gommers > >> mailto:ralf.gomm...@gmail.com>> wrote: > >> > >> > >> > >> On Mon, Mar 27, 2017 at 11:33 PM, Julian Taylor > >> >> <mailto:jtaylor.deb...@googlemail.com>> wrote: > >> > >> I have two ideas under one big important topic: make numpy > >> python3 > >> compatible. > >> > >> The first fits pretty well with the grant size and nobody > >> wants to do it > >> for free: > >> - fix our text IO functions under python3 and support > multiple > >> encodings, not only latin1. > >> Reasonably simple to do, slap encoding arguments on the > >> functions, > >> generate test cases and somehow keep backward compatibility. > >> Some > >> prelimary unfinished work is in > >> https://github.com/numpy/numpy/pull/4208 > >> <https://github.com/numpy/numpy/pull/4208> > >> > >> > >> I like that idea, it's a recurring pain point. Are you > >> interested to work on it, or are you thinking to advertise the > >> idea here to see if anyone steps up? > >> > >> > >> More thoughts on this anyone? Or preferences for this idea or the > >> numpy.org <http://numpy.org> one? Submission deadline is April 3rd > >> and we can only put in one proposal this time, so we need to (a) > >> make a choice between these ideas, and (b) write up a proposal. > >> > >> If there's not enough replies to this so the choice is clear cut, I > >> will send out a poll to the core devs. > >> > >> > >> Do we have anyone interested in doing the work in either case? That > >> seems like the most important consideration to me... > >> > >> -n > >> > > > > I could do the textio thing if no one shows up for numpy.org. I can > > probably check again what is required in the next few days and write a > > proposal. > > The change will need reviewing in the end too, should that be > > compensated too? It feels weird if not. > > > > I have decided to not do it, as it is more or less just a bugfix and I > currently do not feel capable of doing with added completion pressure. > But I have collected some of related issues and discussions: > > https://github.com/numpy/numpy/issues/4600 > https://github.com/numpy/numpy/issues/3184 > http://numpy-discussion.10968.n7.nabble.com/using-loadtxt- > to-load-a-text-file-in-to-a-numpy-array-tt35992.html#a36003 > # loadtxt > https://github.com/numpy/numpy/pull/4208 > # genfromtxt > http://numpy-discussion.10968.n7.nabble.com/genfromtxt- > universal-newline-support-td37816.html > https://github.com/dhomeier/numpy/commit/995ec93 > ___ > NumPy-Discussion mailing list > NumPy-Discussion@python.org > https://mail.python.org/mailman/listinfo/numpy-discussion > -- Renato Fabbri GNU/Linux User #479299 labmacambira.sourceforge.net ___ NumPy-Discussion mailing list NumPy-Discussion@python.org https://mail.python.org/mailman/listinfo/numpy-discussion
[Numpy-discussion] power function distribution or power-law distribution?
numpy.random.power.__doc__ uses only the term "power function distribution". I cannot find a comparison between this term and "power-law distribution" and am quite interested to know if they are simply synonyms. Any ideas? BTW. how is this list related to numpy-discuss...@scipy.org? -- Renato Fabbri GNU/Linux User #479299 labmacambira.sourceforge.net ___ NumPy-Discussion mailing list NumPy-Discussion@python.org https://mail.python.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] power function distribution or power-law distribution?
Thanks for the reply. But the question remains: how are the terms "power function distribution" and "power-law distribution" related? The documentation link you sent have no information on this. ( And seems the same as I get here In [6]: n.version.full_version Out[6]: '1.11.0' ) On Thu, Aug 24, 2017 at 11:07 AM, Pauli Virtanen wrote: > to, 2017-08-24 kello 10:53 -0300, Renato Fabbri kirjoitti: > > numpy.random.power.__doc__ > > > > uses only the term "power function distribution". > > The documentation in the most recent Numpy version seems to be more > explicit, see the Notes section for the PDF: > > https://docs.scipy.org/doc/numpy/reference/generated/numpy.random.power > .html > > > BTW. how is this list related to numpy-discuss...@scipy.org? > > That's the old address of this list. > The current address is numpy-discussion@python.org and it should be > used instead. > > -- > Pauli Virtanen > ___ > NumPy-Discussion mailing list > NumPy-Discussion@python.org > https://mail.python.org/mailman/listinfo/numpy-discussion > -- Renato Fabbri GNU/Linux User #479299 labmacambira.sourceforge.net ___ NumPy-Discussion mailing list NumPy-Discussion@python.org https://mail.python.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] power function distribution or power-law distribution?
On Thu, Aug 24, 2017 at 11:47 AM, Nathan Goldbaum wrote: > The latest version of numpy is 1.13. > > In this case, as described in the docs, a power function distribution is > one with a probability desnity function of the form ax^(a-1) for x between > 0 and 1. > ok, let's try ourselves to relate the terms. Would you agree that the "power function distribution" is a "power-law distribution" in which the domain is restricted to be [0,1]? > > On Thu, Aug 24, 2017 at 9:41 AM, Renato Fabbri > wrote: > >> Thanks for the reply. >> >> But the question remains: >> how are the terms "power function distribution" >> and "power-law distribution" related? >> >> The documentation link you sent have no information on this. >> ( >> And seems the same as I get here >> In [6]: n.version.full_version >> Out[6]: '1.11.0' >> ) >> >> On Thu, Aug 24, 2017 at 11:07 AM, Pauli Virtanen wrote: >> >>> to, 2017-08-24 kello 10:53 -0300, Renato Fabbri kirjoitti: >>> > numpy.random.power.__doc__ >>> > >>> > uses only the term "power function distribution". >>> >>> The documentation in the most recent Numpy version seems to be more >>> explicit, see the Notes section for the PDF: >>> >>> https://docs.scipy.org/doc/numpy/reference/generated/numpy.random.power >>> .html >>> <https://docs.scipy.org/doc/numpy/reference/generated/numpy.random.power.html> >>> >>> > BTW. how is this list related to numpy-discuss...@scipy.org? >>> >>> That's the old address of this list. >>> The current address is numpy-discussion@python.org and it should be >>> used instead. >>> >>> -- >>> Pauli Virtanen >>> ___ >>> NumPy-Discussion mailing list >>> NumPy-Discussion@python.org >>> https://mail.python.org/mailman/listinfo/numpy-discussion >>> >> >> >> >> -- >> Renato Fabbri >> GNU/Linux User #479299 >> labmacambira.sourceforge.net >> >> ___ >> NumPy-Discussion mailing list >> NumPy-Discussion@python.org >> https://mail.python.org/mailman/listinfo/numpy-discussion >> >> > > ___ > NumPy-Discussion mailing list > NumPy-Discussion@python.org > https://mail.python.org/mailman/listinfo/numpy-discussion > > -- Renato Fabbri GNU/Linux User #479299 labmacambira.sourceforge.net ___ NumPy-Discussion mailing list NumPy-Discussion@python.org https://mail.python.org/mailman/listinfo/numpy-discussion
[Numpy-discussion] floor with dtype
""" In [3]: n.floor(n.linspace(0,5,7), dtype=n.int) --- TypeError Traceback (most recent call last) in () > 1 n.floor(n.linspace(0,5,7), dtype=n.int) TypeError: No loop matching the specified signature and casting was found for ufunc floor In [4]: n.__version__ Out[4]: '1.11.0' """ Is this the expected behavior? I am doing: >>> myints = n.array(n.floor(myarray), dtype=n.int) to get the integers. tx. R. -- Renato Fabbri GNU/Linux User #479299 labmacambira.sourceforge.net ___ NumPy-Discussion mailing list NumPy-Discussion@python.org https://mail.python.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] floor with dtype
I have an array of floats and
want their floor values as integers.
(e.g. to use them as indexes for a table lookup)
It seems reasonable to assume this is
a frequent use of floor.
Anyway, you gave me a better vay to do it:
>>> myints = n.floor(myarray).astype(n.int)
On Mon, Sep 25, 2017 at 7:23 AM, Thomas Jollans wrote:
> On 2017-09-25 10:59, Renato Fabbri wrote:
> > """
> > In [3]: n.floor(n.linspace(0,5,7), dtype=n.int <http://n.int>)
> >
> ---
> > TypeError Traceback (most recent call
> last)
> > in ()
> > > 1 n.floor(n.linspace(0,5,7), dtype=n.int <http://n.int>)
> >
> > TypeError: No loop matching the specified signature and casting
> > was found for ufunc floor
> >
> > In [4]: n.__version__
> > Out[4]: '1.11.0'
> > """
> >
> > Is this the expected behavior?
>
> Yes. There is no floor function for integers.
>
> The dtype argument specified not only the return type, but the type the
> calculation is done in as well. floor() only exists, and only makes
> sense, for floats. (You can use floor(a, dtype='f4') and so on to insist
> on floats of a different width)
>
> If you have some floats, and you want to get their floor as integers,
> you'll have to cast. In that case, in actual fact, there is little
> reason to use floor at all:
>
> In [2]: np.arange(1.9, 11.)
> Out[2]: array([ 1.9, 2.9, 3.9, 4.9, 5.9, 6.9, 7.9, 8.9,
> 9.9, 10.9])
>
> In [3]: np.arange(1.9, 11.).astype('i8')
> Out[3]: array([ 1, 2, 3, 4, 5, 6, 7, 8, 9, 10])
>
>
> >
> > I am doing:
> >>>> myints = n.array(n.floor(myarray), dtype=n.int <http://n.int>)
> > to get the integers.
> >
> > tx.
> > R.
> >
> >
> > --
> > Renato Fabbri
> > GNU/Linux User #479299
> > labmacambira.sourceforge.net <http://labmacambira.sourceforge.net>
> >
> >
> > _______
> > NumPy-Discussion mailing list
> > NumPy-Discussion@python.org
> > https://mail.python.org/mailman/listinfo/numpy-discussion
> >
>
>
> --
> Thomas Jollans
> ___
> NumPy-Discussion mailing list
> NumPy-Discussion@python.org
> https://mail.python.org/mailman/listinfo/numpy-discussion
>
--
Renato Fabbri
GNU/Linux User #479299
labmacambira.sourceforge.net
___
NumPy-Discussion mailing list
NumPy-Discussion@python.org
https://mail.python.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] floor with dtype
>>> myarray.astype(n.int) returns the same values as >>> n.floor(myarray).astype(n.int) for positive values?? And the same as >>> n.trunc(myarray) for any value? On Mon, Sep 25, 2017 at 5:36 PM, Mark Bakker wrote: > > On 2017-09-25 10:59, Renato Fabbri wrote: > >> > > """ >> > > In [3]: n.floor(n.linspace(0,5,7), dtype=n.int <http://n.int>) >> > > >> > --- >> > > TypeError Traceback (most recent call >> > last) >> > > in () >> > > > 1 n.floor(n.linspace(0,5,7), dtype=n.int <http://n.int>) >> > > >> > > TypeError: No loop matching the specified signature and casting >> > > was found for ufunc floor >> > > >> > > In [4]: n.__version__ >> > > Out[4]: '1.11.0' >> > > """ >> > > >> > > Is this the expected behavior? >> > >> > Yes. There is no floor function for integers. >> > >> > The dtype argument specified not only the return type, but the type the >> > calculation is done in as well. floor() only exists, and only makes >> > sense, for floats. (You can use floor(a, dtype='f4') and so on to insist >> > on floats of a different width) >> > > +1 for specifying a dtype in np.floor and np.ceil. > > Now it is pretty odd that np.floor and np.ceil results in an integer, > except for that it doesn't. it returns a float with all zeros as the > decimals. It would be very useful to be able to specify the dtype at 'int'. > I frequently use floor or ceil to determine the indices of an array, but > now need to convert to integers in addition to floor and ceil. > > > ___ > NumPy-Discussion mailing list > NumPy-Discussion@python.org > https://mail.python.org/mailman/listinfo/numpy-discussion > > -- Renato Fabbri GNU/Linux User #479299 labmacambira.sourceforge.net ___ NumPy-Discussion mailing list NumPy-Discussion@python.org https://mail.python.org/mailman/listinfo/numpy-discussion
[Numpy-discussion] doc? music through mathematical relations between LPCM samples and musical elements/characteristics
the half-shape suite: archive.org/details/ShapeSuite was completely synthesized using psychophysical relations for each resulting 16bit 44kHz samples: https://arxiv.org/abs/1412.6853 I am thinking about the ways in which to make the documentation at least to: * mass (music and audio in sample sequences): the framework. It might be considered a toolbox, but it is not a package: https://github.com/ttm/mass/ * music: a package for making music, including the routines used to make the half-shape suite: https://github.com/ttm/music == It seems reasonable at first to: * upload the package to PyPI (mass is not a package), music is there (beta but there). * Make available some summary of the file tree, including some automated code documentation. As I follow numpy's convention (or try to), and the package and framework are particularly useful for proficient numpy users, I used Sphinx. The very preliminary version is: https://pythonmusic.github.io/ * Make a nice readthedocs documentation. "music" project name was taken so I made: http://music-documentation.readthedocs.io/en/latest/ "mass" project name was also taken so I made: http://musicmass.readthedocs.io/en/latest/ And I found these URLs clumsy. Is there a standard or would you go with musicpackage.read.. and massframework.read... ? More importantly: * would you use readthedocs for the sphinx/doxigen output? * would you use readthedocs.org or a gitbook would be better or...? Should I contact the scipy community to make available a scikit or integrate it to numpy in any way beyond using and citing it appropriately?. BTW. I am using vimwiki with some constant attempt to organize and track my I/O: https://arxiv.org/abs/1712.06933 So maybe a unified solution for all these documentation instances using a wiki structure seems reasonable at the moment. Maybe upload the generated html from Sphinx and from Vimwiki to readthedocs...? Best, R. -- Renato Fabbri GNU/Linux User #479299 labmacambira.sourceforge.net ___ NumPy-Discussion mailing list NumPy-Discussion@python.org https://mail.python.org/mailman/listinfo/numpy-discussion
[Numpy-discussion] documentation, sound and music [was: doc? music through mathematical relations between LPCM samples and musical elements/characteristics]
Dear Scipy-ers, If you think I should split the message so that things get more clear... But the things are: 1) How to document numpy-heavy projects? 2) How to better make these contributions available to the numpy/scipy community? Directions will be greatly appreciated. I suspect that this info is all gathered somewhere I did not find. PS. I apologize for the cross-post, this is a message sent to numpy list but without any replies, so I found fit to send the message to both lists. Thanks in advance, Best, R. -- Forwarded message -- From: Renato Fabbri Date: Tue, Jan 30, 2018 at 8:32 PM Subject: doc? music through mathematical relations between LPCM samples and musical elements/characteristics To: Discussion of Numerical Python the half-shape suite: archive.org/details/ShapeSuite was completely synthesized using psychophysical relations for each resulting 16bit 44kHz samples: https://arxiv.org/abs/1412.6853 I am thinking about the ways in which to make the documentation at least to: * mass (music and audio in sample sequences): the framework. It might be considered a toolbox, but it is not a package: https://github.com/ttm/mass/ * music: a package for making music, including the routines used to make the half-shape suite: https://github.com/ttm/music == It seems reasonable at first to: * upload the package to PyPI (mass is not a package), music is there (beta but there). * Make available some summary of the file tree, including some automated code documentation. As I follow numpy's convention (or try to), and the package and framework are particularly useful for proficient numpy users, I used Sphinx. The very preliminary version is: https://pythonmusic.github.io/ * Make a nice readthedocs documentation. "music" project name was taken so I made: http://music-documentation.readthedocs.io/en/latest/ "mass" project name was also taken so I made: http://musicmass.readthedocs.io/en/latest/ And I found these URLs clumsy. Is there a standard or would you go with musicpackage.read.. and massframework.read... ? More importantly: * would you use readthedocs for the sphinx/doxigen output? * would you use readthedocs.org or a gitbook would be better or...? Should I contact the scipy community to make available a scikit or integrate it to numpy in any way beyond using and citing it appropriately?. BTW. I am using vimwiki with some constant attempt to organize and track my I/O: https://arxiv.org/abs/1712.06933 So maybe a unified solution for all these documentation instances using a wiki structure seems reasonable at the moment. Maybe upload the generated html from Sphinx and from Vimwiki to readthedocs...? Best, R. -- Renato Fabbri GNU/Linux User #479299 labmacambira.sourceforge.net -- Renato Fabbri GNU/Linux User #479299 labmacambira.sourceforge.net ___ NumPy-Discussion mailing list NumPy-Discussion@python.org https://mail.python.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] documentation, sound and music [was: doc? music through mathematical relations between LPCM samples and musical elements/characteristics]
I think you gave me the answers: 0) It seems reasonable to just use sphinx, no jekyll or anything more, only if a need for it is found. I might use some HTML generated by vimwiki for pure convenience. 1) Make the main documentation with sphinx. That means joining: and 2) github.io, gitbook, readthedocs, all is just as fine. Maybe github.io makes it easier and has more features, while readthedocs is maybe more traditional for these kinds of python-related docs. 3) just realese on pypi, make the documentation fine and tell the list. If any major release deserves a message, it is ok to send. 3.1) A scikit to make psychoacoutic experiments, synthesize audio and music, is not absurd nor deeply compelling. 4) Am I loosing something? Being mindful of this question is always good, but that is it, we are on track. (the python and latex files are on github, so there is an issue tracker, a wiki etc etc there if anything comes up) tx++ On Wed, Jan 31, 2018 at 9:20 PM, Robert Kern wrote: > On Thu, Feb 1, 2018 at 7:38 AM, Renato Fabbri > wrote: > > > > Dear Scipy-ers, > > > > If you think I should split the message so that > > things get more clear... > > > > But the things are: > > 1) How to document numpy-heavy projects? > > There is nothing particularly special about numpy-heavy projects with > respect to documentation. The tools used for numpy and scipy's > documentation may (or may not) be useful to you. For example, you may want > to embed matplotlib plots into your documentation. > > https://pypi.python.org/pypi/numpydoc > > But if not, don't worry about it. Sphinx is all most numpy-heavy projects > need, like most Python projects. Hosting the documentation on either > readthedocs or Github is fine. Do whatever's convenient for you. Either is > just as convenient for us. > > > 2) How to better make these contributions available > > to the numpy/scipy community? > > Having it up on Github and PyPI is all you need to do. Participate in > relevant mailing list conversations. While we don't forbid release > announcement emails on either of the lists, I wouldn't do much more than > announce the initial release and maybe a really major update (i.e. not for > every bugfix release). > > > Directions will be greatly appreciated. > > I suspect that this info is all gathered somewhere > > I did not find. > > Sorry this isn't gathered anywhere, but truly, the answer is "there is not > much to it". You're doing everything right. :-) > > -- > Robert Kern > > ___ > NumPy-Discussion mailing list > NumPy-Discussion@python.org > https://mail.python.org/mailman/listinfo/numpy-discussion > > -- Renato Fabbri GNU/Linux User #479299 labmacambira.sourceforge.net ___ NumPy-Discussion mailing list NumPy-Discussion@python.org https://mail.python.org/mailman/listinfo/numpy-discussion
[Numpy-discussion] Re: NumPy Development Meeting Wednesday - Triage Focus
On Tue, May 3, 2022 at 1:48 PM Sebastian Berg wrote: > Hi all, > > Our bi-weekly triage-focused NumPy development meeting is Wednesday, > May 4th at 16:00 UTC (9:00am Pacific Time). > Everyone is invited to join in and edit the work-in-progress meeting > topics and notes: > https://hackmd.io/68i_JvOYQfy9ERiHgXMPvg --> 502 Bad Gateway > > > I encourage everyone to notify us of issues or PRs that you feel should > be prioritized, discussed, or reviewed. > > A calendar to can be found at: https://scientific-python.org/calendars/ > please make sure to not import the static `ics` but the url. > > Best regards > > Sebastian > > ___ > NumPy-Discussion mailing list -- numpy-discussion@python.org > To unsubscribe send an email to numpy-discussion-le...@python.org > https://mail.python.org/mailman3/lists/numpy-discussion.python.org/ > Member address: renato.fab...@gmail.com > -- Renato Fabbri -- ___ NumPy-Discussion mailing list -- numpy-discussion@python.org To unsubscribe send an email to numpy-discussion-le...@python.org https://mail.python.org/mailman3/lists/numpy-discussion.python.org/ Member address: arch...@mail-archive.com
[Numpy-discussion] Numpy-related jobs, grants, etc
This is not only for me, but a question for the community in general. Do we have an open knowledge base of budget (interested companies or individuals, public funding) for developing numpy-related packages? Explaining a bit with a specific case... In the last few years, I have many times thought about the possibility of working with Numpy: finding payment for developing libraries using Numpy or even Numpy internals. Especially, I have written a music python library (called 'music' on PyPI). It holds many useful things, equal-loudness contours, musical notes, localization, HRTF, LUT, singing, glissandi, tremolos & vibratos with transitions, etc etc. I believe it is something well done, which involved scientific research and over a decade of experience with the algorithms, but it still lacks a better organization of the functionalities, better documentation, and better maintenance. To reach that point, one would probably have to be paid to take the necessary time. Beyond that, I know it is useful for making art/music, teaching, learning music, learning music-related signal processing and programming, etc. Maybe the most important point: this is probably the case with other libraries/projects. ((( On the other side, we as a company (here at Modena/Italy) may look into (public, private, own) funding to develop Numpy (internals, libraries). We would also enjoy developing Numpy-related libraries (internals?) if someone needs or wants them. ))) Should this be posted in another list/forum? Any thoughts? R. -- Renato Fabbri -- ___ NumPy-Discussion mailing list -- numpy-discussion@python.org To unsubscribe send an email to numpy-discussion-le...@python.org https://mail.python.org/mailman3/lists/numpy-discussion.python.org/ Member address: arch...@mail-archive.com
