Mailman 3 March 2019 - SciPy-Dev

Google Season of Docs
by Christoph Baumgarten April 2, 2019

April 2, 2019

Hi, taking up Ralf's mail on GSoD, I had a look at the website and propose to apply. My project suggestion would be to work on the documentation of a module like stats: - improve the tutorial site https://docs.scipy.org/doc/scipy/reference/tutorial/stats.html - improve the documentation of the API - check whether current descriptions can be improved - add examples and references - cross-ref to other relevant / similar functions in the module The second point would require decent knowledge of statistics whereas the first point should be easier to tackle for a technical writer. So I see the second point as optional and one could also try to work on the tutorial site of more than one module during the 3-month period. The task would leave quite a bit of freedom to the writer to choose what areas to focus on, potentially taking up some of the documentation issues that are already on Github. I could assist as a mentor for stats (we need at least two mentors). Any suggestions or comments? Christoph

2 2

GSoC 2019
by Gopi Manohar Tatiraju April 2, 2019

April 2, 2019

I want to work on SciPy in GSoC 2019. I started fixing some bugs, also made some pull request. Can anyone suggest me how should I proceed further?

4 20

GSoC 2019
by Anany Shrey Jain March 31, 2019

March 31, 2019

Hey, Thanks Greg and Eric for the new ideas and suggestions about the implementation of API. I have updated the page with greater details about the implementation of each approach. I have started it with explaining each approach and in the end I tried to club all these approaches to get something better. Please have a look: https://github.com/ananyashreyjain/Gsoc-Scipy/wiki/Gsoc-2019:-Scipy cheers, Anany Jain. On Sun, Mar 31, 2019 at 5:23 AM <scipy-dev-request(a)python.org> wrote: > Send SciPy-Dev mailing list submissions to > scipy-dev(a)python.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://mail.python.org/mailman/listinfo/scipy-dev > or, via email, send a message with subject or body 'help' to > scipy-dev-request(a)python.org > > You can reach the person managing the list at > scipy-dev-owner(a)python.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of SciPy-Dev digest..." > > > Today's Topics: > > 1. Re: GSoC 2019 (Eric Larson) > 2. Re: GSoC 2019 (Gregory Lee) > 3. Re: GSoC 2019 (Gregory Lee) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Sat, 30 Mar 2019 13:31:51 -0400 > From: Eric Larson <larson.eric.d(a)gmail.com> > To: SciPy Developers List <scipy-dev(a)python.org> > Subject: Re: [SciPy-Dev] GSoC 2019 > Message-ID: > < > CAGu2niVWsKrMukfWcAWAtj-1NBm2utCeh3BOnNku7jNoAcx-kw(a)mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > It looks like the main ideas are in these bits of code, but not explicitly > stated. In brief it looks like the proposed API is to add a `fft_object` > kwarg to every function in `scipy.fftpack`. It would be good to discuss > this choice explicitly -- what advantages and disadvantages it has relative > to other approaches (e.g., creating new namespaces, or having a > `set_backend` function (and/or context manager) that would change things > under the hood). > > If you make changes and need more feedback, let us know. The more specific > you can be about what you need feedback on (high level ideas, low level > implementation, etc.), the better. > > Eric > > > On Fri, Mar 29, 2019 at 4:12 AM Anany Shrey Jain < > f20170920(a)goa.bits-pilani.ac.in> wrote: > > > Hey, > > I went through the idea list of Scipy for this years's GSoC and I intend > > to work towards the idea of revamping the Scipy's fftpack. I have already > > been contributing to Scipy since the end of last year and I have some > > knowledge about Fourier transforms as it was the part of my discipline. I > > could not take part in this discussion earlier because my mid semester > > exams were going on, but since they are now over so I can devote as much > > time as required on this project. I have already created a github page > with > > some code snippets and functionalities that we can implement, here is the > > link to it: > > https://github.com/ananyashreyjain/Gsoc-Scipy/wiki/Gsoc-2019:-Scipy . > > > > Cheers, > > Anany Jain > > > > _______________________________________________ > > SciPy-Dev mailing list > > SciPy-Dev(a)python.org > > https://mail.python.org/mailman/listinfo/scipy-dev > > >

1 0

GSoC 2019
by Anany Shrey Jain March 30, 2019

March 30, 2019

Hey, I went through the idea list of Scipy for this years's GSoC and I intend to work towards the idea of revamping the Scipy's fftpack. I have already been contributing to Scipy since the end of last year and I have some knowledge about Fourier transforms as it was the part of my discipline. I could not take part in this discussion earlier because my mid semester exams were going on, but since they are now over so I can devote as much time as required on this project. I have already created a github page with some code snippets and functionalities that we can implement, here is the link to it: https://github.com/ananyashreyjain/Gsoc-Scipy/wiki/Gsoc-2019:-Scipy . Cheers, Anany Jain

3 2

genfromtxt
by Nicholas Alexeev March 29, 2019

March 29, 2019

I noticed that the genfromtxt() function is slow and it consumes a large amount of memory. I am trying to improve it. Does anyone have any tips? Thanks.

3 2

Add `is_feasible` and `violated_excess` to PreparedConstraint
by Andrew Nelson March 28, 2019

March 28, 2019

As part of an idea to add constraints to differential_evolution I'd like to add an `is_feasible` and `violated_excess` method to `optimize._constaints.PreparedConstraint`. The `is_feasible` method would return the truth of whether a given solution satisfies the constraint. The `violated_excess` method would give the total amount that the constraint is violated by; for example if ub=[5, 6] and the constraint evaluates to [5.5, 10], then the total excess would be 4.5. I fully appreciate that `violated_excess` is a silly name, and welcome suggestions for an alternative. -- _____________________________________ Dr. Andrew Nelson _____________________________________

1 0

ANN: SfePy 2019.1
by Robert Cimrman March 26, 2019

March 26, 2019

I am pleased to announce release 2019.1 of SfePy. Description ----------- SfePy (simple finite elements in Python) is a software for solving systems of coupled partial differential equations by the finite element method or by the isogeometric analysis (limited support). It is distributed under the new BSD license. Home page: http://sfepy.org Mailing list: https://mail.python.org/mm3/mailman3/lists/sfepy.python.org/ Git (source) repository, issue tracker: https://github.com/sfepy/sfepy Highlights of this release -------------------------- - automatic fallback for linear solvers - quadratic eigenvalue problem solver For full release notes see [1]. Cheers, Robert Cimrman [1] http://docs.sfepy.org/doc/release_notes.html#id1 --- Contributors to this release in alphabetical order: Robert Cimrman Lubos Kejzlar Vladimir Lukes

1 0

Non linear constraints for differential evolution
by Andrew Nelson March 19, 2019

March 19, 2019

Dear list, I've been musing on the implementation of non-linear constraints for `scipy.optimize.differential_evolution`. There are various ways of doing this (search for "nonlinear constraint function differential evolution" on Google). There is a version by Lampinen (2002) that seems fairly straightforward. It is described at: https://pdfs.semanticscholar.org/088e/60df2694230e8e9e841e19ec218cddba54fe.… The paper has been cited 263 times, which indicates its usefulness. These kinds of constraints have been implemented in the R version (as indicated by the documentation). Does anyone else have any thoughts as to whether they'd find such an approach useful in scipy? Andrew. -- _____________________________________ Dr. Andrew Nelson _____________________________________

2 1

Fwd: Announcement and thanks to Season of Docs survey respondents: Season of Docs has launched
by Ralf Gommers March 12, 2019

March 12, 2019

It's official, Season of Docs is happening! Does look very interesting, I'd love to see NumPy and SciPy participate. Ralf ---------- Forwarded message --------- From: Sarah Maddox <sarahmaddox(a)google.com> Date: Mon, Mar 11, 2019 at 2:56 PM Subject: Announcement and thanks to Season of Docs survey respondents: Season of Docs has launched To: Thank you for your feedback on the initial proposal of Google’s Season of Docs program! You’re receiving this email because you indicated that you’d like us to send you updates about the program. We’re delighted to announce that we’ve launched the 2019 pilot of Season of Docs. Details are on our website: g.co/seasonofdocs <https://developers.google.com/season-of-docs/>. Season of Docs is a Google program that fosters collaboration between open source projects and technical writers. It’s similar to Summer of Code, but with a focus on documentation and technical writers. Would you like to take part as a mentor in the inaugural year of Season of Docs? Organization applications open on April 2, 2019. See the full timeline <https://developers.google.com/season-of-docs/docs/timeline> and join the announcement group at season-of-docs-announce <https://groups.google.com/group/season-of-docs-announce> to stay informed. Please do tweet and blog about Season of Docs if you’d like to share the news. We want as many people to know about it as possible. We’ve provided logos that you can download and some example content on the press page <https://developers.google.com/season-of-docs/docs/press>. If you have any questions, please email season-of-docs-support(a)googlegroups.com. Many thanks again for your valuable feedback on the initial proposal. Sarah Maddox, Andrew Chen, and the Season of Docs team

2 2

SciPy GSOC 2019
by saif ali March 4, 2019

March 4, 2019

Thanks to all, till now my all doubts have been cleared so I will start working on the project and proposal, I will surely ask if I encounter further problems. Cheers.

1 0