Re: [sympy] Re: Removing duplication of evaluation and refine logic

> Note that your benchmark is flawed since it creates an AssumptionsWrapper each time in the timing loop. If we only want to make a single call to is_positive then we could have a function that does that without creating a new Basic instance. Otherwise the AssumptionsWrapper is created so that

Re: [sympy] My GSOC Proposal for Sympy Live and Gamma

You should go into more details about how you plan to implement the various features. Note that most of the work currently needed for SymPy Live is related to the backend architecture (see https://github.com/sympy/sympy/wiki/GSoC-Ideas#sympy-live-and-sympy-gamma-on-google-app-engine). Aaron

Re: [sympy] Drop support for Theano and support Aesara instead

On Wed, Mar 31, 2021 at 12:18 PM Brandon T. Willard wrote: > > > > But if you can't actually make any changes > or releases for it, then you can't actually do that, and have no > choice but to fork. > > Yeah, that was essentially the situation. > > > SymPy uses unevaluated expressions > (or

Re: [sympy] Parsing ideas in Sympy

I've added a question here Idea for a AST frontend for parsing between Julia and Python - Tooling - JuliaLang . Interestingly, it seems there is a Sympy.jl

Re: [sympy] PhD Looking for ideas to collaborate with Sympy.

Hi Patricio, Being able to compute the Galois group of a polynomial would be nice. I have no idea how you do that... Are there algorithms for that that don't require computing expressions for the roots? Another thing lacking in sympy is an implementation of finite fields of non-prime order.

Re: [sympy] Drop support for Theano and support Aesara instead

> But if you can't actually make any changes or releases for it, then you can't actually do that, and have no choice but to fork. Yeah, that was essentially the situation. > SymPy uses unevaluated expressions (or "graphs" as the tensor people call it, which is a term I'm not fond of)... Aren't

Re: [sympy] PhD Looking for ideas to collaborate with Sympy.

Patricio, Here's our starting point for new contributors: https://github.com/sympy/sympy/wiki/introduction-to-contributing It sounds like you have in-depth knowledge so I'm sure you'll find nice holes you can fill and grow. Jason moorepants.info +01 530-601-9791 On Wed, Mar 31, 2021 at 3:42

Re: [sympy] Re: Removing duplication of evaluation and refine logic

On Wed, 31 Mar 2021 at 15:05, JSS95 wrote: > > Assumptions are used only in ask() and refine(), so __new__() does not need > to take assumptions. Besides, using new assumption in __new__() will make > everything extremely slow so I'd say __new__() must not take assumptions. Agreed > My idea

Re: [sympy] Re: Removing duplication of evaluation and refine logic

Assumptions are used only in ask() and refine(), so __new__() does not need to take assumptions. Besides, using new assumption in __new__() will make everything extremely slow so I'd say __new__() must not take assumptions. My idea is to make eval() method, not __new__(), able to take

[sympy] PhD Looking for ideas to collaborate with Sympy.

I'm Patricio. I want to participate with the main goal of Sympy. So I want to collaborate to the implementation Computation of Galois groups for a given polynomial or I can collaborate with something else closed to my background. Then I'm here looking for ideas. I have a PhD in Mathematics,

Re: [sympy] Re: Removing duplication of evaluation and refine logic

Hi Jissoo, I think that the real question is how are we going to refactor the evaluation code to make it possible to supply an assumptions argument? At the moment the evaluation is typically in __new__ and no __new__ methods take an assumptions argument. We can't pass an assumptions argument to

Re: [sympy] ODE solver roadmap

Hi Nijso, > Great to see that you are making so much progress in such a short time! Thank you! I have to say that you are really helping a lot creating a roadmap that can help the ODE module a lot. Infact, the Riccati solver wasn't even being considered until you talked about it! > You must

Re: [sympy] ODE solver roadmap

Hi Naveen, Great to see that you are making so much progress in such a short time! Regarding your question: >I'm unable to understand how to compute solutions symbolically when the value of "m" is unknown. Is it possible? I can use sympy's assumptions to make sure that m.is_integer gives

Re: [sympy] Re: Simplifying expressions involving the Abs function

Dear Chris, On 31.03.21 05:48, Chris Smith wrote: Oscar posted code at issue https://github.com/sympy/sympy/issues/19164 for a interva-based Newton solver. Thank you, that's very useful. I didn't know about interval arithmetic. I just implemented the following, which works very well and

[sympy] Re: Removing duplication of evaluation and refine logic

Here is the performance for three suggestions. Suggestion 3 is the fastest, and for me it looks cleaner than the others. [image: suggestions.PNG] 2021년 3월 31일 수요일 오후 3시 24분 38초 UTC+9에 JSS95님이 작성: > In SymPy, we have two ways to get the mathematical property of an object : > the old

[sympy] Removing duplication of evaluation and refine logic

In SymPy, we have two ways to get the mathematical property of an object : the old assumptions system and the new assumptions system. With old assumptions system, the property is accessed by `.is_[...]` attribute. Here, property of the object is intrinsic. ``` In [1]: x = Symbol('x',