[sympy] nice update and notification from GitHub

I appreciate that GitHub listens to its users. The following is the end of an issue that I identified a while back: Hi Chris! > > I just wanted to follow up and let you know that the team pushed out an > update to fix the wiki linking problem you discovered a while back. Thanks > again for the

[sympy] Re: GSOC 2017: SymPy Live and SymPy Gamma (on Google App Engine)

Hi Bhautik, I would look at the issues list for SymPy Live[1] and SymPy Gamma[2]. For SymPy Live, I would say the biggest problem is how it is implemented - it tries to preserve a user session by pickling all globals, but this does not always work, and so it falls back to re-evaluating

Re: [sympy] SymPy Live Maintainer

Yes, please ping me on Github or email me if there's anything in the code that isn't clear. Long term I'm hoping WebAssembly will mean we can run sessions in-browser, though having to download the Python stdlib would make this not ideal for people on slow/metered connections. There is a PR to

Re: [sympy] SymPy Live Maintainer

That's great. SymPy Live is in need of some maintainence. I'm CCing David Li, who has written most of the code. I think the biggest issue with SymPy Live is the way it does evaluation. Because it runs on the App Engine, which only allows persistence for 60 seconds, commands are re-executed (I

[sympy] SymPy Live Maintainer

Hello everyone, My name is Ivan Savov and I'm a long time SymPy user, especially SymPy live. The SymPy Live shell is doing well, but there hasn't been much updates recently. I wanted to let everyone know that I'm available to contribute by fixing bugs and keeping the

Re: [sympy] GSOC 2017 idea: non-rigid body

You can have two proposals that work on related things, but each proposal needs to stand on its own (that is, if only one proposal gets accepted, you should still be able to do the work). Aaron Meurer On Tue, Mar 28, 2017 at 3:15 PM, Tatyana Abramova wrote: > As far as I

Re: [sympy] GSOC 2017 idea: non-rigid body

Tatyana, There are projects that have enough work to share between two proposals. That would be ok. But all of the proposals should be primarily focused on developing software for SymPy. Each proposal should be focused on the software additions and changes that the student will work on during the

[sympy] Re: Implementation of a user-defined coordinate system

If one created subgroups, this be a case where instances would work? On Tuesday, March 28, 2017 at 4:06:41 PM UTC-4, Mikayla Z. Grace wrote: > > Okay, I think I must have misunderstood what you were saying. Are you > saying you think a single superclass is better than individual classes? > >

[sympy] Re: Implementation of a user-defined coordinate system

Okay, I think I must have misunderstood what you were saying. Are you saying you think a single superclass is better than individual classes? On Tuesday, March 28, 2017 at 3:20:03 PM UTC-4, Francesco Bonazzi wrote: > > There should be one class for all coordinate systems because they are the >

[sympy] Re: Implementation of a user-defined coordinate system

There should be one class for all coordinate systems because they are the same objects. -- You received this message because you are subscribed to the Google Groups "sympy" group. To unsubscribe from this group and stop receiving emails from it, send an email to

Re: [sympy] GSOC 2017 idea: non-rigid body

As far as I understand, we are allowed to do one project together, but we should write separated proposals where each of us should write about own purposes and objectives. In our project I will deal with the part related to physics, my friend will be engaged in programming, so I supposed to

Re: [sympy] Modelling and finite element analysis

Tedongmo, Welcome to the SymPy community. I suggest asking questions on the mailing list if you are hoping for a response. If you are interested in GSoC, be sure to let us know. Jason moorepants.info +01 530-601-9791 On Mon, Mar 27, 2017 at 1:05 PM, Tedongmo wrote: > Hi

[sympy] Re: Feedback on GSoC Proposal

Changed the link, so here is the new link to the proposal: https://github.com/sympy/sympy/wiki/GSoC-2017-Application-Mikayla-Z.-Grace:-Extend-Implementation-of-Different-Vector-Coordinate-Systems-to-Vector-Functions On Monday, March 27, 2017 at 11:37:07 PM UTC-4, Mikayla Z. Grace wrote: > > I

[sympy] Re: Implementation of a user-defined coordinate system

To clarify, I'm thinking about having classes for the standard coordinate systems and then one additional class for user-defined classes. On Tuesday, March 28, 2017 at 11:06:31 AM UTC-4, Mikayla Z. Grace wrote: > > Looking at some previous work done on vector coordinate systems, it seems >

Re: [sympy] Re: Feedback on GSoC Proposal

I cannot emphasize too strongly to understand the wikipedia article on orthogonal coordinates in 3 dimensions. https://en.wikipedia.org/wiki/Orthogonal_coordinates#Differential_operators_in_three_dimensions There are only 12 possible orthogonal coordinate systems. The formulas given cover

[sympy] Re: Feedback on GSoC Proposal

Arif, thank you! I agree that would strengthen it a lot. Jason, thank you as well! I will take a look at the proposal you sent-- that's very helpful. On Monday, March 27, 2017 at 11:37:07 PM UTC-4, Mikayla Z. Grace wrote: > > I have a first draft of my Google Summer of Code project proposal

[sympy] Implementation of a user-defined coordinate system

Looking at some previous work done on vector coordinate systems, it seems that there have been two major trains of thought: Either we should have each coordinate system be its own class or have a superclass that has subclasses within it (see PR #10109

[sympy] Re: Lots of problems with Stats module

Well, I know the basic stuff like calculating probability using set relations, Binomial distribution, Poission distribution, Law of independent events etc. I have implemented some algorithms involving these basic topics in competitive programming. In statistics I know graphs, histogram, Mean,

Re: [sympy] GSoC: Assumptions Project

Hi, it's slightly out of topic, but SymPy is really missing the ability to define assumptions on sets (that is, that a variable belongs to a set, e.g. x in [1, 3]). There are some PR that could be continued: - https://github.com/sympy/sympy/pull/11615 -

Re: [sympy] Feedback on GSoC Proposal

Mikayla, Have a look at this proposal from last year: https://github.com/sympy/sympy/wiki/GSoC-2016-Application-Sampad-Kumar-Saha:-Singularity-Functions It is a very well designed proposal. Compare yours to it and I think you'll see a number of improvements you can make. I also agree with

[sympy] Re: Feedback on GSoC Proposal

I'm just a student contributer, but I'd say one way to make your proposal stronger is to write down a rough prototype of the different coordinate classes you've mentioned. On Tuesday, March 28, 2017 at 9:07:07 AM UTC+5:30, Mikayla Z. Grace wrote: > > I have a first draft of my Google Summer of