RE: [sympy] GSoC 2024 Contributors Announced
Clear, thank you Aaron! -Original Message- From: sympy@googlegroups.com On Behalf Of Aaron Meurer Sent: Montag, 6. Mai 2024 21:08 To: sympy@googlegroups.com Subject: Re: [sympy] GSoC 2024 Contributors Announced Yes, I probably should have shared this initially, but you can see a list of the projects with their summaries at https://summerofcode.withgoogle.com/programs/2024/organizations/sympy Aaron Meurer On Fri, May 3, 2024 at 12:25 PM wrote: > > Dear Aaron, > > I am happy to join in congratulating the guys selected for GSoC! > > I am a retired salesman (studied engineering 45+ years ago) and I play around > with sympy.phyiscs.mechanics to pass time. VERY enjoyable! > I have never made a PR, and the equation: me + GitHub / computers = complete > messholds true. > > These two projects look interesting to me: > > Hwayeon Kang, Implementing Specific Forces and Torques: Jason Moore, > Timo Stienstra Riccardo Di Girolamo, Sympy for Classical Mechanics: > Developing and Benchmarking Equations of Motion Generation Methods: > Jason Moore, Timo Stienstra > > Is there a way, I can 'see' what will be done there? > > Thanks & take care! > > Peter > > -Original Message- > From: sympy@googlegroups.com On Behalf Of > Aaron Meurer > Sent: Donnerstag, 2. Mai 2024 21:36 > To: sympy > Subject: [sympy] GSoC 2024 Contributors Announced > > Hi everyone. As many of you may have noticed, Google has announced the > results for Google Summer of Code. I am proud to announce that 5 > people have been accepted to work on SymPy this year. The following > projects have been > accepted: > > Abhishek Kumar, Improving and Expanding the functionalities of the > SymPy's Control Module.: Nikhil Maan > > Arnab Nandi, Improving Series Expansions and Limit Computations: > Anutosh Surendra Bhat, Oscar Benjamin > > Hwayeon Kang, Implementing Specific Forces and Torques: Jason Moore, > Timo Stienstra > > Riccardo Di Girolamo, Sympy for Classical Mechanics: Developing and > Benchmarking Equations of Motion Generation Methods: Jason Moore, Timo > Stienstra > > Shishir Kushwaha, Extending Continuum Mechanics Module: Advait Pote, > Ishan Pandhare > > Join me in congratulating them on their acceptance. > > To everyone who was accepted, you should be receiving an email from your > mentors soon to discuss how you will be communicating over the summer about > your project. You should meet with your mentors once a week during the summer > to go over your progress. Most people choose to use video calls for these > meetings, but you may use another method, such as a public chatroom, if you > prefer. > > Note that in many cases you may interact with some mentors as your > primary mentors, and other mentors will be backup mentors. Please > contact the backup mentors if you are not able to get ahold of your > primary mentor(s). If you cannot get ahold of either, please let me > and Oscar Benjamin > (oscar.j.benja...@gmail.com) know immediately. > > I would like all of us to strongly encourage students to submit pull requests > early and often. This will go a long ways towards making sure that you don't > end the summer with a ton of code written that never gets merged. Students > should help review pull requests by other students, so that we don't get > bogged down reviewing so much code. > > We also require that all students keep a weekly blog of their work over the > summer. If you don't already have a blog, you should start one. I recommend > using either Wordpress, Blogger, or creating your own blog on GitHub pages. > If you are savvy enough to set it up, I recommend GitHub pages, but if you > aren't, both Wordpress and Blogger are good enough. > > The GSoC coding period officially starts May 27 > (https://developers.google.com/open-source/gsoc/timeline). > > I would like to thank all the students who applied this year and everyone who > submitted a patch. I would also like to thank all the mentors for helping > review patches and proposals. > > This summer is looking to be another very productive one for SymPy, and I > look forward to it! > > Aaron Meurer > > -- > 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 sympy+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/sympy/CAKgW%3D6%2B6r%2BxD_7DjRR60WuAhnsJkRw6SMWOpwTsnVN0D-JrjKw%40mail.gmail.com. > > -- > 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 sympy+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/sympy/004601da9d87%245093a4d0%24f1baee70%24%40gmail.com. -- You received this message because you are subscribed to the Google Groups "sympy" group. To unsubsc
Re: [sympy] GSoC 2024 Contributors Announced
Yes, I probably should have shared this initially, but you can see a list of the projects with their summaries at https://summerofcode.withgoogle.com/programs/2024/organizations/sympy Aaron Meurer On Fri, May 3, 2024 at 12:25 PM wrote: > > Dear Aaron, > > I am happy to join in congratulating the guys selected for GSoC! > > I am a retired salesman (studied engineering 45+ years ago) and I play around > with sympy.phyiscs.mechanics to pass time. VERY enjoyable! > I have never made a PR, and the equation: me + GitHub / computers = complete > messholds true. > > These two projects look interesting to me: > > Hwayeon Kang, Implementing Specific Forces and Torques: Jason Moore, Timo > Stienstra > Riccardo Di Girolamo, Sympy for Classical Mechanics: Developing and > Benchmarking Equations of Motion Generation Methods: Jason Moore, Timo > Stienstra > > Is there a way, I can 'see' what will be done there? > > Thanks & take care! > > Peter > > -Original Message- > From: sympy@googlegroups.com On Behalf Of Aaron > Meurer > Sent: Donnerstag, 2. Mai 2024 21:36 > To: sympy > Subject: [sympy] GSoC 2024 Contributors Announced > > Hi everyone. As many of you may have noticed, Google has announced the > results for Google Summer of Code. I am proud to announce that 5 people have > been accepted to work on SymPy this year. The following projects have been > accepted: > > Abhishek Kumar, Improving and Expanding the functionalities of the SymPy's > Control Module.: Nikhil Maan > > Arnab Nandi, Improving Series Expansions and Limit Computations: > Anutosh Surendra Bhat, Oscar Benjamin > > Hwayeon Kang, Implementing Specific Forces and Torques: Jason Moore, Timo > Stienstra > > Riccardo Di Girolamo, Sympy for Classical Mechanics: Developing and > Benchmarking Equations of Motion Generation Methods: Jason Moore, Timo > Stienstra > > Shishir Kushwaha, Extending Continuum Mechanics Module: Advait Pote, Ishan > Pandhare > > Join me in congratulating them on their acceptance. > > To everyone who was accepted, you should be receiving an email from your > mentors soon to discuss how you will be communicating over the summer about > your project. You should meet with your mentors once a week during the summer > to go over your progress. Most people choose to use video calls for these > meetings, but you may use another method, such as a public chatroom, if you > prefer. > > Note that in many cases you may interact with some mentors as your primary > mentors, and other mentors will be backup mentors. Please contact the backup > mentors if you are not able to get ahold of your primary mentor(s). If you > cannot get ahold of either, please let me and Oscar Benjamin > (oscar.j.benja...@gmail.com) know immediately. > > I would like all of us to strongly encourage students to submit pull requests > early and often. This will go a long ways towards making sure that you don't > end the summer with a ton of code written that never gets merged. Students > should help review pull requests by other students, so that we don't get > bogged down reviewing so much code. > > We also require that all students keep a weekly blog of their work over the > summer. If you don't already have a blog, you should start one. I recommend > using either Wordpress, Blogger, or creating your own blog on GitHub pages. > If you are savvy enough to set it up, I recommend GitHub pages, but if you > aren't, both Wordpress and Blogger are good enough. > > The GSoC coding period officially starts May 27 > (https://developers.google.com/open-source/gsoc/timeline). > > I would like to thank all the students who applied this year and everyone who > submitted a patch. I would also like to thank all the mentors for helping > review patches and proposals. > > This summer is looking to be another very productive one for SymPy, and I > look forward to it! > > Aaron Meurer > > -- > 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 sympy+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/sympy/CAKgW%3D6%2B6r%2BxD_7DjRR60WuAhnsJkRw6SMWOpwTsnVN0D-JrjKw%40mail.gmail.com. > > -- > 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 sympy+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/sympy/004601da9d87%245093a4d0%24f1baee70%24%40gmail.com. -- 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 sympy+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/sympy/CAKgW%3D6KHA%3D4AXpAuFcVEh3kdcfWNtR
Re: [sympy] Re: Enhancing the flexibility of MatchPy
Hi Francesco, yeah sure, I will proceed in that way. Thanks. On Monday, May 6, 2024 at 2:23:07 AM UTC+5:30 Francesco Bonazzi wrote: > Do you mean forking MatchPy? I would suggest by creating a personal fork > of the project. I would not create a fork of MatchPy on SymPy's space > unless we're really sure about continuing the development of MatchPy. > > On Saturday, May 4, 2024 at 4:18:32 a.m. UTC+2 samithkar...@gmail.com > wrote: > >> Hi Aaron, >> Thank you for the reply, I would like to give it try. In-order to >> contribute to this project, I need to have a fork of this repository in >> somewhere (Sympy org or else). So If someone can help me with that I will >> try to contribute. >> >> Best Regards, >> Samith Karunathilake. >> >> On Friday, May 3, 2024 at 2:54:28 AM UTC+5:30 asme...@gmail.com wrote: >> >>> Hi Samith. >>> >>> You are always free to contribute to SymPy independently of GSoC, as >>> it is an open source project and you can always contribute to an open >>> source project. We can't guarantee you the mentorship that a GSoC >>> contributor would receive. It would be up to Francesco and other >>> community members if he is interested in helping out with this >>> project. >>> >>> Aaron Meurer >>> >>> On Wed, May 1, 2024 at 7:58 PM Samith Kavishke >>> wrote: >>> > >>> > Hi, >>> > Eventhough have not been selected, do we still have a chance to >>> continue the project? Without the stipend. >>> > >>> > On Tuesday, April 2, 2024 at 7:14:15 AM UTC+5:30 Samith Kavishke >>> wrote: >>> >> >>> >> I have attached the changed version of this project. Thank you! >>> >> >>> >> On Monday, April 1, 2024 at 2:43:25 PM UTC+5:30 Samith Kavishke >>> wrote: >>> >>> >>> >>> I will go through it and try to suggest a new method if time >>> permits. Thank you Francesco you helped a lot to achieve this amount. >>> >>> >>> >>> On Monday, April 1, 2024 at 2:27:15 PM UTC+5:30 Francesco Bonazzi >>> wrote: >>> >>> The issue I see in the proposal is that the methods should probably >>> be functions, not class methods. If we keep class methods we are probably >>> still forced to use subclassing (I would like to avoid that). Anyways, it >>> looks good, this is just a minor issue >>> >>> On Tuesday, March 26, 2024 at 12:07:15 p.m. UTC+1 Francesco Bonazzi >>> wrote: >>> > >>> > The base idea is about modifying MatchPy in order to allow easy >>> integration of MatchPy into SymPy and into the python bindings of protosym. >>> Additional extensions to the project idea are welcome, provided there is >>> enough time to complete them. Trying a translation of MatchPy into Rust has >>> the potential of speeding up the library a lot, but it should be >>> benchmarked. >>> > >>> > On Tuesday, March 26, 2024 at 2:54:23 a.m. UTC+1 >>> samithkar...@gmail.com wrote: >>> >> >>> >> Is it worth for me to mention about the Protosym's architecture, >>> in order to strengthen my proposal ? or do I need more contributions in >>> sympy repositories. >>> >> >>> >> On Sunday, March 24, 2024 at 4:29:40 AM UTC+5:30 Samith Kavishke >>> wrote: >>> >>> >>> >>> Hi, >>> >>> Thank you, Francesco for your valuable insights. I have attached >>> my current draft of GSOC 24 proposal. Can you help me with feedbacks for >>> the proposal. >>> >>> >>> >>> >>> >>> On Tuesday, March 19, 2024 at 8:15:07 PM UTC+5:30 Francesco >>> Bonazzi wrote: >>> >>> No, no parsers are needed. Just a tree traversal for-loop. It's >>> already implemented: >>> >>> iterator >>> iterator size >>> >>> As you see, in the current implementation we need to use >>> @op_iter.register... because "op_iter" is a MatchPy function that does not >>> exist in SymPy... With @op_iter.register we can extend it to a SymPy >>> object. The problem is: >>> >>> @op_iter.register is an almost hackish way to do it, it messes >>> up with the class inheritance. We need something easier to use. >>> The .register method defines the iterator on a class. We may >>> have cases in which we would like to have different iterators for the same >>> class... so it shouldn't be a class method. >>> >>> >>> On Monday, March 18, 2024 at 11:20:10 p.m. UTC+1 >>> samithkar...@gmail.com wrote: >>> > >>> > I think, I understood the point you are making. If we are >>> going to redefine the tree structure in matchpy using overridable methods, >>> does that mean we have to use a parser to translate the sympy object type >>> to matchpy or are there any better way to handle the situation. >>> > On Saturday, March 16, 2024 at 8:32:03 PM UTC+5:30 Francesco >>> Bonazzi wrote: >>> >> >>> >> I suggest to start the unit tests of MatchPy in debug mode >>> and follow the tree traversal to get some more insight. Indeed, the
