Re: [sympy] Re: Project Idea and Expression of Interest

2024-03-30 Thread Shishir Kushwaha
The Proposal 

Kindly take a look at the new Phases and the revised timeline ,I have set 
aside some time for the extended goal which can be used to complete work of 
other phases in case it was not possible earlier.
I'd be happy to receive any reviews and changes before submission.

Shishir
On Sunday 31 March 2024 at 02:08:58 UTC+5:30 Shishir Kushwaha wrote:

> Thank you for the review sir. 
>
> About the point on the time taken for Phase 2 , the current code included 
> with the proposal was written with a very intuitive approach but I would 
> like to follow similar approaches to the ones used in Beams and Trusses 
> using various inbuilt functions like Singularity Function whose discussion 
> and implementation might take some extra time.
>
> According to my current understanding , I might be able to cut out about 2 
> weeks from the entire duration of the project for the extended phase if the 
> implementation goes smoothly however I wanted some extra time so I don't 
> promise more things than I might be able to achieve.
> I will be making the changes recommended and report as soon as possible.
>
>
> Shishir
>
> On Sunday 31 March 2024 at 00:18:31 UTC+5:30 apot...@gmail.com wrote:
>
>> Your proposal seems very detailed and your contributions are good too. 
>>
>> One minor change I'd suggest is instead of adding screenshots of your 
>> code from your editor, try using any add-ons on Google Docs that enable you 
>> to write code. This is purely for presentation purposes though. 
>> About the timeline, you should rename 'Phase 3' as 'Extended Phase' 
>> because it isn't a part of your project and isn't included in your 
>> timeline. 
>> Finally, I don't think you should add the code for everything. Maybe a 
>> few snippets showing the implementation here and there but not your entire 
>> project. Try using pseudo code for some or maybe not even that. Also, if 
>> you are already done with the code for a lot of the project, maybe you can 
>> reduce the time for Phase II and try including the extended phase in your 
>> timeline. Assigning 9 weeks for a Phase for which you are quite prepared 
>> seems a little excessive and I think your project would look better with 3 
>> phases rather than just 2.
>>
>> On Sat, Mar 30, 2024 at 1:50 AM Shishir Kushwaha  
>> wrote:
>>
>>> The Proposal 
>>> 
>>> Can you please take a look at it and recommend any changes or 
>>> suggestions that may be added. I am sorry for the delay, due to some 
>>> unexpected circumstances I could not complete it earlier. 
>>>
>>> Shishir
>>> On Wednesday 20 March 2024 at 01:37:55 UTC+5:30 apot...@gmail.com wrote:
>>>
 I don't think there should be a problem with sending the draft in this 
 thread itself. Will be glad to look at it. 

 On Mon, Mar 18, 2024 at 12:09 PM Shishir Kushwaha <
 kushwahas...@gmail.com> wrote:

> I have been working on my proposal for some time, can I please get 
> some time from your schedule to get your thoughts and improve on it 
> before 
> the final submission? 
> I would also like to know if there are some additional ideas I should 
> add along with my current proposal. 
> If possible where should I send my draft proposal?
>
> Sincerely
> Shishir Kushwaha   
>
> On Wednesday 6 March 2024 at 23:24:47 UTC+5:30 apot...@gmail.com 
> wrote:
>
>> Your ideas seem good. The cable class doesn't have a draw method and 
>> could use it considering how the other classes do. The ILD functionality 
>> does look promising too. 
>>
>> I haven't heard or read much about Arches as I believe they are 
>> inclined towards Civil Engineering and Architecture. I will be 
>> interested 
>> to see your approach & thoughts and how you structure them in your 
>> proposal. 
>>
>> On Tuesday, March 5, 2024 at 1:25:06 AM UTC+5:30 
>> kushwahas...@gmail.com wrote:
>>
>>> Respected Sympy community ,
>>>
>>>
>>> My name is Shishir Kushwaha ,currently a sophomore at Indian 
>>> Institute of Technology , BHU ,Varanasi , India . I am currently 
>>> pursuing a 
>>> degree in Mathematics and Computing and my interest lies in fields 
>>> related 
>>> to mathematics, physics and machine learning and have worked on honing 
>>> my 
>>> skills in the domains . Having used Sympy to help me through my 
>>> projects 
>>> related to Mechanical Engineering , I found it very useful and would 
>>> like 
>>> to help others in the same way by further improving its features in the 
>>> same direction .  
>>>
>>>
>>> I would like to express my interest in contributing to Sympy in the 
>>> GSoC 2024 program . The ability to symbolically solve complex problems 
>>> and 

Re: [sympy] Re: Project Idea and Expression of Interest

2024-03-30 Thread Shishir Kushwaha
Thank you for the review sir. 

About the point on the time taken for Phase 2 , the current code included 
with the proposal was written with a very intuitive approach but I would 
like to follow similar approaches to the ones used in Beams and Trusses 
using various inbuilt functions like Singularity Function whose discussion 
and implementation might take some extra time.

According to my current understanding , I might be able to cut out about 2 
weeks from the entire duration of the project for the extended phase if the 
implementation goes smoothly however I wanted some extra time so I don't 
promise more things than I might be able to achieve.
I will be making the changes recommended and report as soon as possible.


Shishir

On Sunday 31 March 2024 at 00:18:31 UTC+5:30 apot...@gmail.com wrote:

> Your proposal seems very detailed and your contributions are good too. 
>
> One minor change I'd suggest is instead of adding screenshots of your code 
> from your editor, try using any add-ons on Google Docs that enable you to 
> write code. This is purely for presentation purposes though. 
> About the timeline, you should rename 'Phase 3' as 'Extended Phase' 
> because it isn't a part of your project and isn't included in your 
> timeline. 
> Finally, I don't think you should add the code for everything. Maybe a few 
> snippets showing the implementation here and there but not your entire 
> project. Try using pseudo code for some or maybe not even that. Also, if 
> you are already done with the code for a lot of the project, maybe you can 
> reduce the time for Phase II and try including the extended phase in your 
> timeline. Assigning 9 weeks for a Phase for which you are quite prepared 
> seems a little excessive and I think your project would look better with 3 
> phases rather than just 2.
>
> On Sat, Mar 30, 2024 at 1:50 AM Shishir Kushwaha  
> wrote:
>
>> The Proposal 
>> 
>> Can you please take a look at it and recommend any changes or suggestions 
>> that may be added. I am sorry for the delay, due to some unexpected 
>> circumstances I could not complete it earlier. 
>>
>> Shishir
>> On Wednesday 20 March 2024 at 01:37:55 UTC+5:30 apot...@gmail.com wrote:
>>
>>> I don't think there should be a problem with sending the draft in this 
>>> thread itself. Will be glad to look at it. 
>>>
>>> On Mon, Mar 18, 2024 at 12:09 PM Shishir Kushwaha <
>>> kushwahas...@gmail.com> wrote:
>>>
 I have been working on my proposal for some time, can I please get some 
 time from your schedule to get your thoughts and improve on it before the 
 final submission? 
 I would also like to know if there are some additional ideas I should 
 add along with my current proposal. 
 If possible where should I send my draft proposal?

 Sincerely
 Shishir Kushwaha   

 On Wednesday 6 March 2024 at 23:24:47 UTC+5:30 apot...@gmail.com wrote:

> Your ideas seem good. The cable class doesn't have a draw method and 
> could use it considering how the other classes do. The ILD functionality 
> does look promising too. 
>
> I haven't heard or read much about Arches as I believe they are 
> inclined towards Civil Engineering and Architecture. I will be interested 
> to see your approach & thoughts and how you structure them in your 
> proposal. 
>
> On Tuesday, March 5, 2024 at 1:25:06 AM UTC+5:30 
> kushwahas...@gmail.com wrote:
>
>> Respected Sympy community ,
>>
>>
>> My name is Shishir Kushwaha ,currently a sophomore at Indian 
>> Institute of Technology , BHU ,Varanasi , India . I am currently 
>> pursuing a 
>> degree in Mathematics and Computing and my interest lies in fields 
>> related 
>> to mathematics, physics and machine learning and have worked on honing 
>> my 
>> skills in the domains . Having used Sympy to help me through my projects 
>> related to Mechanical Engineering , I found it very useful and would 
>> like 
>> to help others in the same way by further improving its features in the 
>> same direction .  
>>
>>
>> I would like to express my interest in contributing to Sympy in the 
>> GSoC 2024 program . The ability to symbolically solve complex problems 
>> and 
>> ability to integrate well when needed due to it being coded in pure 
>> Python 
>> makes it an exciting project to anyone with a mathematical background . 
>>
>>
>> I looked through the ideas list page and liked a few projects I would 
>> like to work on . I would like to further the module on continuum 
>> mechanics 
>> by implementing plotting of draw and tension to the newer Cable Class 
>> along 
>> with an influence line diagram functionality . Along with this I hope to 
>> introduce and complete the implementation of structures like Arches 

Re: [sympy] Re: Improving .subs() method issue

2024-03-30 Thread HAWK
Thank you sangyub for such detailed explanation, I really appreciate it. I
think you are right if we implement such algo for .subs(), it will just
make things complex. But was thinking that if we could try such things may
be it would make way better and I think there is a way to make it work. I
will write you back if I can make things work like I explained.

On Sat, 30 Mar 2024 at 20:30, Sangyub Lee  wrote:

> I may give the step-by-step technical explanation why eq.subs works this
> way:
>
> - The subexpressions of x**2 + 5 are x**2, and 5, which is eq.args
> - The subexpressions of x**2 are x and 2, which is (x**2).args
> - There are no subexpressions of 5, because 5 is an atom.
> - There are no subexpressions of 2, because 2 is an atom.
> - There are no subexpressions of x, because x is an atom.
>
> And the subs, (reasonably) works when the expression that is substituted,
> is equal to the expression, or its subexpressions.
> x is recursively the subexpression of x**2 + 5, so eq.subs(x, 1) works,
> however, x+1 is not the subexpression of  x**2 + 5, so eq.subs(x+1,2)
> works.
>
> Although this is not 100% everything about how subs works, however, I
> think that it explains fairly most of the logic about the subs,
> and I hope it can be useful for your programming experience with subs.
> The reason that subs(x+1, 2) does not work, is debatable that it should be
> a bug, or it should be intended part of the design,
>
> However, I'm weighted towards the opinion that it shouldn't be part of the
> design,
> because it is much more complicated and opens up much more rooms for
> extension or incompleteness, if we adopt that as part of the design.
> For example, if subs(x+1, 2) works, then we should also think of how
> subs(x**2 + 1, 2), or how subs(x**3 + 1, 2) works,
> and I'm afraid that such discussions like this clearly gets into
> discussing very complicated mathematics that you or me are not familiar
> with.
>
> On Friday, March 29, 2024 at 10:04:03 AM UTC+1 thakur.ompra...@gmail.com
> wrote:
>
>> Hello SymPy community,
>> I want to ask if you guys allow me I would like to raise a issue or we
>> can say improvement. I found .subs() amusing but I think we can upgrade
>> that. For reference when we have a equation eq=x**2+5 and then we use
>> eq.subs(x,1) it means x is replaced by 1(x-->1), that gives a simple answer
>> 6. That's totally fine but if I want to substitute a expression with
>> something, it won't work let's take the previous example, eq=x**2+5 and
>> then we use eq.subs(x+1,2) this gives old equation back, but it was
>> supposed to replace x+1 to 2 that means same as before (x-->1) and answer
>> supposed to be 6 as in real mathematics.
>> [image: Screenshot 2024-03-29 141816.png]
>>
> --
> 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/8ab1f6bc-55c1-462a-837e-400341c8d0e7n%40googlegroups.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/CAG2MUzs4kYijrQC9Zq88mWBc2XjF4ss-gRSCFcj%3DLw83-Ct4hw%40mail.gmail.com.


Re: [sympy] Re: Project Idea and Expression of Interest

2024-03-30 Thread Advait Pote
Your proposal seems very detailed and your contributions are good too.

One minor change I'd suggest is instead of adding screenshots of your code
from your editor, try using any add-ons on Google Docs that enable you to
write code. This is purely for presentation purposes though.
About the timeline, you should rename 'Phase 3' as 'Extended Phase'
because it isn't a part of your project and isn't included in your
timeline.
Finally, I don't think you should add the code for everything. Maybe a few
snippets showing the implementation here and there but not your entire
project. Try using pseudo code for some or maybe not even that. Also, if
you are already done with the code for a lot of the project, maybe you can
reduce the time for Phase II and try including the extended phase in your
timeline. Assigning 9 weeks for a Phase for which you are quite prepared
seems a little excessive and I think your project would look better with 3
phases rather than just 2.

On Sat, Mar 30, 2024 at 1:50 AM Shishir Kushwaha <
kushwahashishir1...@gmail.com> wrote:

> The Proposal
> 
> Can you please take a look at it and recommend any changes or suggestions
> that may be added. I am sorry for the delay, due to some unexpected
> circumstances I could not complete it earlier.
>
> Shishir
> On Wednesday 20 March 2024 at 01:37:55 UTC+5:30 apot...@gmail.com wrote:
>
>> I don't think there should be a problem with sending the draft in this
>> thread itself. Will be glad to look at it.
>>
>> On Mon, Mar 18, 2024 at 12:09 PM Shishir Kushwaha 
>> wrote:
>>
>>> I have been working on my proposal for some time, can I please get some
>>> time from your schedule to get your thoughts and improve on it before the
>>> final submission?
>>> I would also like to know if there are some additional ideas I should
>>> add along with my current proposal.
>>> If possible where should I send my draft proposal?
>>>
>>> Sincerely
>>> Shishir Kushwaha
>>>
>>> On Wednesday 6 March 2024 at 23:24:47 UTC+5:30 apot...@gmail.com wrote:
>>>
 Your ideas seem good. The cable class doesn't have a draw method and
 could use it considering how the other classes do. The ILD functionality
 does look promising too.

 I haven't heard or read much about Arches as I believe they are
 inclined towards Civil Engineering and Architecture. I will be interested
 to see your approach & thoughts and how you structure them in your
 proposal.

 On Tuesday, March 5, 2024 at 1:25:06 AM UTC+5:30 kushwahas...@gmail.com
 wrote:

> Respected Sympy community ,
>
>
> My name is Shishir Kushwaha ,currently a sophomore at Indian Institute
> of Technology , BHU ,Varanasi , India . I am currently pursuing a degree 
> in
> Mathematics and Computing and my interest lies in fields related to
> mathematics, physics and machine learning and have worked on honing my
> skills in the domains . Having used Sympy to help me through my projects
> related to Mechanical Engineering , I found it very useful and would like
> to help others in the same way by further improving its features in the
> same direction .
>
>
> I would like to express my interest in contributing to Sympy in the
> GSoC 2024 program . The ability to symbolically solve complex problems and
> ability to integrate well when needed due to it being coded in pure Python
> makes it an exciting project to anyone with a mathematical background .
>
>
> I looked through the ideas list page and liked a few projects I would
> like to work on . I would like to further the module on continuum 
> mechanics
> by implementing plotting of draw and tension to the newer Cable Class 
> along
> with an influence line diagram functionality . Along with this I hope to
> introduce and complete the implementation of structures like Arches
> allowing similar functionalities in Beams and Trusses .
>
>
> I would like to request the mentors Ishan Pandhare , Advait Pote ,
> Prakhar Saxena to kindly take a look and check if it aligns with the goals
> of Sympy and is a suitable idea for GSoC 2024 .
>
>
> I am familiar with Python , Pytorch and JavaScript stacks with
> experience in many relevant projects of web development and mathematical
> implementations of Digital Image Processing .
>
> I hope my technical skills along with my dedication would allow me to
> successfully execute my duties .
>
>
> Thank you for your time and consideration , I hope to work and learn
> with the amazing Sympy Community .
>
>
> Sincerely ,
>
> Shishir Kushwaha
>
>
> --
>>> 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 

[sympy] Re: Improving .subs() method issue

2024-03-30 Thread Sangyub Lee
I may give the step-by-step technical explanation why eq.subs works this 
way:

- The subexpressions of x**2 + 5 are x**2, and 5, which is eq.args
- The subexpressions of x**2 are x and 2, which is (x**2).args
- There are no subexpressions of 5, because 5 is an atom.
- There are no subexpressions of 2, because 2 is an atom.
- There are no subexpressions of x, because x is an atom.

And the subs, (reasonably) works when the expression that is substituted, 
is equal to the expression, or its subexpressions.
x is recursively the subexpression of x**2 + 5, so eq.subs(x, 1) works,
however, x+1 is not the subexpression of  x**2 + 5, so eq.subs(x+1,2) works.

Although this is not 100% everything about how subs works, however, I think 
that it explains fairly most of the logic about the subs, 
and I hope it can be useful for your programming experience with subs.
The reason that subs(x+1, 2) does not work, is debatable that it should be 
a bug, or it should be intended part of the design,

However, I'm weighted towards the opinion that it shouldn't be part of the 
design, 
because it is much more complicated and opens up much more rooms for 
extension or incompleteness, if we adopt that as part of the design.
For example, if subs(x+1, 2) works, then we should also think of how 
subs(x**2 + 1, 2), or how subs(x**3 + 1, 2) works,
and I'm afraid that such discussions like this clearly gets into discussing 
very complicated mathematics that you or me are not familiar with.

On Friday, March 29, 2024 at 10:04:03 AM UTC+1 thakur.ompra...@gmail.com 
wrote:

> Hello SymPy community,
> I want to ask if you guys allow me I would like to raise a issue or we can 
> say improvement. I found .subs() amusing but I think we can upgrade that. 
> For reference when we have a equation eq=x**2+5 and then we use 
> eq.subs(x,1) it means x is replaced by 1(x-->1), that gives a simple answer 
> 6. That's totally fine but if I want to substitute a expression with 
> something, it won't work let's take the previous example, eq=x**2+5 and 
> then we use eq.subs(x+1,2) this gives old equation back, but it was 
> supposed to replace x+1 to 2 that means same as before (x-->1) and answer 
> supposed to be 6 as in real mathematics.
> [image: Screenshot 2024-03-29 141816.png]
>

-- 
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/8ab1f6bc-55c1-462a-837e-400341c8d0e7n%40googlegroups.com.