date:20170112

Re: [sympy] Re: Doing a release

2017-01-12 Thread Aaron Meurer

So how do they deal with merge conflicts in the file? I don't want
people to constantly be having to fix their branches because the
release notes file has conflicts from another merge.

Aaron Meurer

On Thu, Jan 12, 2017 at 8:57 AM, Shekhar Prasad Rajak
 wrote:
> The
> Files(https://github.com/pandas-dev/pandas/tree/master/doc/source/whatsnew)
> are written by hand with the PR. Means whenever a bug is fixed PR author
> must add the testcase for the bug, and also update the file. Similarly
> whenever anything new features implemented.
>
> See this PR :
> https://github.com/pandas-dev/pandas/commit/0fe491db358204544814aa2371fed4ea947532ab#diff-52364fb643114f3349390ad6bcf24d8fR286
> . This PR fix the issue : #15048   and same is updated in the file
> (whatsnew/v0.20.0.txt) by the PR author.
>
> --
> Shekhar
>
> On Monday, 26 September 2016 22:43:16 UTC+5:30, Aaron Meurer wrote:
>>
>> Now that GSoC has wrapped up, we should start looking at doing a release.
>> As a start, can people
>>
>> - Mark issues and pull requests that need to be completed before the
>> release with the "SymPy 1.1" milestone
>>
>> - Update the release notes with changes that have been merged
>> https://github.com/sympy/sympy/wiki/Release-Notes-for-1.1
>>
>> Any help you can provide on the above two points (especially the release
>> notes) would be greatly appreciated.
>>
>> 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 post to this group, send email to sympy@googlegroups.com.
> Visit this group at https://groups.google.com/group/sympy.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/sympy/d1f76e72-c2bd-4801-ab09-f3d94b0f2785%40googlegroups.com.
>
> For more options, visit https://groups.google.com/d/optout.

-- 
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 post to this group, send email to sympy@googlegroups.com.
Visit this group at https://groups.google.com/group/sympy.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sympy/CAKgW%3D6LWKJsCkhM4hXBMoPV4q5GDTGOcrYPc94RYGNR8v8bhAg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[sympy] Re: SingularityFunction in sympy.physics.continuum_mechanics.beam

2017-01-12 Thread SAMPAD SAHA

What I feel is that :

Since you are considering concentrated load of 6 N at the middle only and
both the ends are fixed then only the following part of the code would
suffice the solution-

In [81]: b5 = Beam(4, E, I)
In [82]: b5.bc_deflection = [(0, 0), (4, 0)]
In [83]: b5.apply_load(-R1, 0, -1)
In [84]: b5.apply_load(-R2, 4, -1)
In [85]: b5.apply_load(6, 2, -1)
In [86]: b5.solve_for_reaction_loads(R1, R2)
In [87]: b5.reaction_loads
Out[87]: {R2: 3, R1: 3}

Jason, Can you please verify if I am applying correct logic?



Regards
Sampad Kumar Saha
Mathematics and Computing
I.I.T. Kharagpur

On Thu, Jan 12, 2017 at 7:40 PM, SAMPAD SAHA  wrote:

>
>
> -- Forwarded message --
> From: Durve Sanjiv (External) 
> Date: Thu, Jan 12, 2017 at 6:40 PM
> Subject: RE: SingularityFunction in sympy.physics.continuum_mechanics.beam
> To: SAMPAD SAHA 
>
>
> Sampad,
>
>
>
> Thanks for your reply and interest. You can add Sympy group in this thread
> – I have no problem just send me a link.
>
>
>
> I think my question was not very clear. I am sorry about that.
>
>
>
> My problem is a beam fixed at both ends with a concentrated load of 6
> units in the center. Theoretical answer for M1 and M2 is 6*4/8 = 3.
>
>
>
> When I run the following script,
>
>
>
> from sympy.physics.continuum_mechanics.beam import Beam
>
> from sympy.functions import SingularityFunction
>
> from sympy import symbols, Piecewise, plot
>
> E, I, x = symbols('E, I, x')
>
> R1, R2 = symbols('R1, R2')
>
> M1, M2 = symbols('M1, M2')
>
> b = Beam(4, E, I)
>
> b.apply_load(R1, 0, -1)
>
> b.apply_load(6, 2, -1)
>
> b.apply_load(R2, 4, -1)
>
> b.apply_load(M1, 0, -1)
>
> b.apply_load(M2, 4, -1)
>
> b.bc_deflection = [(0, 0), (4, 0)]
>
> b.bc_slope  = [(0, 0), (4, 0)]
>
> print b.boundary_conditions
>
> #b.solve_for_reaction_loads(R1, R2)
>
> b.solve_for_reaction_loads(R1, R2,M1,M2)
>
> print b.load
>
> print b.shear_force()
>
> print b.bending_moment()
>
> print b.slope().subs({E:1,I:1})
>
> print b.deflection().subs({E:1,I:1})
>
>
>
>
>
> I get following output
>
>
>
>
>
>
>
> In [*2*]: runfile('C:/UserApps/Python27/Lib/site-packages/xy/problem01.py',
> wdir='C:/UserApps/Python27/Lib/site-packages/xy')
>
> {'slope': [(0, 0), (4, 0)], 'deflection': [(0, 0), (4, 0)]}
>
> M1*SingularityFunction(x, 0, -1) + M2*SingularityFunction(x, 4, -1) + (-M1
> - 3)*SingularityFunction(x, 0, -1) + (-M2 - 3)*SingularityFunction(x, 4,
> -1) + 6*SingularityFunction(x, 2, -1)
>
> M1*SingularityFunction(x, 0, 0) + M2*SingularityFunction(x, 4, 0) + (-M1 -
> 3)*SingularityFunction(x, 0, 0) + (-M2 - 3)*SingularityFunction(x, 4, 0) +
> 6*SingularityFunction(x, 2, 0)
>
> M1*SingularityFunction(x, 0, 1) + M2*SingularityFunction(x, 4, 1) + (-M1 -
> 3)*SingularityFunction(x, 0, 1) + (-M2 - 3)*SingularityFunction(x, 4, 1) +
> 6*SingularityFunction(x, 2, 1)
>
> Traceback (most recent call last):
>
>
>
> File "", line 1, in 
>
> runfile('C:/UserApps/Python27/Lib/site-packages/xy/problem01.py',
> wdir='C:/UserApps/Python27/Lib/site-packages/xy')
>
>
>
> File "C:\UserApps\Python27\lib\site-packages\spyderlib\widgets\
> externalshell\sitecustomize.py", line 685, in runfile
>
> execfile(filename, namespace)
>
>
>
> File "C:\UserApps\Python27\lib\site-packages\spyderlib\widgets\
> externalshell\sitecustomize.py", line 71, in execfile
>
> exec(compile(scripttext, filename, 'exec'), glob, loc)
>
>
>
> File "C:/UserApps/Python27/Lib/site-packages/xy/problem01.py", line 28,
> in 
>
> print b.slope().subs({E:1,I:1})
>
>
>
> File "C:\UserApps\Python27\lib\site-packages\sympy-1.0.1.dev0-
> py2.7.egg\sympy\physics\continuum_mechanics\beam.py", line 455, in slope
>
> slope_curve = slope_curve.subs({C3: constants[0][0]})
>
>
>
> IndexError: list index out of range
>
>
>
> In [*3*]: b.reaction_loads
>
> Out[*3*]: {M2: M2, M1: M1, R2: -M2 - 3, R1: -M1 - 3}
>
> I expect to get something like {R2:-3,R1:-3,M1:3, M1:3}
>
> I can understand that the problem I am trying to solve has indeterminacy
> of 2 and that is why my script is missing some additional statements.
>
> Once this appears in the thread, I will pursue this because it is an
> intersting problem for a hobbyist like me.
>
> Thanks for the help.
>
>
>
> Regards,
>
> Sanjiv Durve
>
> Ex- I I T Kanpur (1976)
>
>
>
> *From:* SAMPAD SAHA [mailto:sampadsa...@gmail.com]
> *Sent:* 12 January 2017 12:34
> *To:* Durve Sanjiv (External)
> *Subject:* Re: SingularityFunction in sympy.physics.continuum_mechan
> ics.beam
>
>
>
> Sorry for the late reply.
>
>
>
> I tried it in my system. I am getting {R2: -3, R1: -3} as output for the
> reaction forces.
>
> Can you please share us your outputs and also the problem statement which
> you are trying to solve?
>
>
>
> And one more thing, it is absolutely fine contacting me directly at my
> gmail but still it is more preferrable that you post these queries into
> the Sympy group and CC other developers. This way you don't have

[sympy] Fwd: SingularityFunction in sympy.physics.continuum_mechanics.beam

2017-01-12 Thread SAMPAD SAHA

-- Forwarded message --
From: Durve Sanjiv (External) 
Date: Thu, Jan 12, 2017 at 6:40 PM
Subject: RE: SingularityFunction in sympy.physics.continuum_mechanics.beam
To: SAMPAD SAHA 

Sampad,

Thanks for your reply and interest. You can add Sympy group in this thread
– I have no problem just send me a link.

I think my question was not very clear. I am sorry about that.

My problem is a beam fixed at both ends with a concentrated load of 6 units
in the center. Theoretical answer for M1 and M2 is 6*4/8 = 3.

When I run the following script,

from sympy.physics.continuum_mechanics.beam import Beam

from sympy.functions import SingularityFunction

from sympy import symbols, Piecewise, plot

E, I, x = symbols('E, I, x')

R1, R2 = symbols('R1, R2')

M1, M2 = symbols('M1, M2')

b = Beam(4, E, I)

b.apply_load(R1, 0, -1)

b.apply_load(6, 2, -1)

b.apply_load(R2, 4, -1)

b.apply_load(M1, 0, -1)

b.apply_load(M2, 4, -1)

b.bc_deflection = [(0, 0), (4, 0)]

b.bc_slope  = [(0, 0), (4, 0)]

print b.boundary_conditions

#b.solve_for_reaction_loads(R1, R2)

b.solve_for_reaction_loads(R1, R2,M1,M2)

print b.load

print b.shear_force()

print b.bending_moment()

print b.slope().subs({E:1,I:1})

print b.deflection().subs({E:1,I:1})

I get following output

In [*2*]: runfile('C:/UserApps/Python27/Lib/site-packages/xy/problem01.py',
wdir='C:/UserApps/Python27/Lib/site-packages/xy')

{'slope': [(0, 0), (4, 0)], 'deflection': [(0, 0), (4, 0)]}

M1*SingularityFunction(x, 0, -1) + M2*SingularityFunction(x, 4, -1) + (-M1
- 3)*SingularityFunction(x, 0, -1) + (-M2 - 3)*SingularityFunction(x, 4,
-1) + 6*SingularityFunction(x, 2, -1)

M1*SingularityFunction(x, 0, 0) + M2*SingularityFunction(x, 4, 0) + (-M1 -
3)*SingularityFunction(x, 0, 0) + (-M2 - 3)*SingularityFunction(x, 4, 0) +
6*SingularityFunction(x, 2, 0)

M1*SingularityFunction(x, 0, 1) + M2*SingularityFunction(x, 4, 1) + (-M1 -
3)*SingularityFunction(x, 0, 1) + (-M2 - 3)*SingularityFunction(x, 4, 1) +
6*SingularityFunction(x, 2, 1)

Traceback (most recent call last):

File "", line 1, in 

runfile('C:/UserApps/Python27/Lib/site-packages/xy/problem01.py',
wdir='C:/UserApps/Python27/Lib/site-packages/xy')

File "C:\UserApps\Python27\lib\site-packages\spyderlib\
widgets\externalshell\sitecustomize.py", line 685, in runfile

execfile(filename, namespace)

File "C:\UserApps\Python27\lib\site-packages\spyderlib\
widgets\externalshell\sitecustomize.py", line 71, in execfile

exec(compile(scripttext, filename, 'exec'), glob, loc)

File "C:/UserApps/Python27/Lib/site-packages/xy/problem01.py", line 28, in

print b.slope().subs({E:1,I:1})

File "C:\UserApps\Python27\lib\site-packages\sympy-1.0.1.
dev0-py2.7.egg\sympy\physics\continuum_mechanics\beam.py", line 455, in
slope

slope_curve = slope_curve.subs({C3: constants[0][0]})

IndexError: list index out of range

In [*3*]: b.reaction_loads

Out[*3*]: {M2: M2, M1: M1, R2: -M2 - 3, R1: -M1 - 3}

I expect to get something like {R2:-3,R1:-3,M1:3, M1:3}

I can understand that the problem I am trying to solve has indeterminacy of
2 and that is why my script is missing some additional statements.

Once this appears in the thread, I will pursue this because it is an
intersting problem for a hobbyist like me.

Thanks for the help.

Regards,

Sanjiv Durve

Ex- I I T Kanpur (1976)

*From:* SAMPAD SAHA [mailto:sampadsa...@gmail.com]
*Sent:* 12 January 2017 12:34
*To:* Durve Sanjiv (External)
*Subject:* Re: SingularityFunction in sympy.physics.continuum_mechanics.beam

Sorry for the late reply.

I tried it in my system. I am getting {R2: -3, R1: -3} as output for the
reaction forces.

Can you please share us your outputs and also the problem statement which
you are trying to solve?

And one more thing, it is absolutely fine contacting me directly at my
gmail but still it is more preferrable that you post these queries into the
Sympy group and CC other developers. This way you don't have to wait for
long and can get very quick response as there are many active developers
working on Sympy currently.

If you don't mind Can I add Sympy Group in this thread?

Regards

Sampad Kumar Saha

Mathematics and Computing

I.I.T. Kharagpur

On Tue, Jan 10, 2017 at 10:29 PM, Durve Sanjiv (External) <
sanjiv.durve.gu...@saipem.com> wrote:

Hello Sampad,

I have been trying to solve a fixed beam problem with concentrated load at
the center of the beam using sympy. You seem to have done a wonderful job
of implementing SingularityFunction. I hope you don’t mind me contacting
you directly at your gmail.

I have the following code which does not give the correct bending moment at
the fixed ends. The line * b.bc_slope  = [(0, 0), (4, 0)]  *seems to
have no effect

Is there a quick fix or let me know if I am missing something. I also tried
introducing M1, M2 and then commented out (shown in bold lines)

Your help would be

[sympy] Re: Doing a release

2017-01-12 Thread Shekhar Prasad Rajak

The Files(
https://github.com/pandas-dev/pandas/tree/master/doc/source/whatsnew) are 
written by hand with the PR. Means whenever a bug is fixed PR author must 
add the testcase for the bug, and also update the file. Similarly whenever 
anything new features implemented. 

See this PR : 
https://github.com/pandas-dev/pandas/commit/0fe491db358204544814aa2371fed4ea947532ab#diff-52364fb643114f3349390ad6bcf24d8fR286
 . 
This PR fix the issue : #15048   and same is updated in the file (
whatsnew/v0.20.0.txt 
)
 
by the PR author.

--
Shekhar

On Monday, 26 September 2016 22:43:16 UTC+5:30, Aaron Meurer wrote:
>
> Now that GSoC has wrapped up, we should start looking at doing a release. 
> As a start, can people
>
> - Mark issues and pull requests that need to be completed before the 
> release with the "SymPy 1.1" milestone
>
> - Update the release notes with changes that have been merged 
> https://github.com/sympy/sympy/wiki/Release-Notes-for-1.1
>
> Any help you can provide on the above two points (especially the release 
> notes) would be greatly appreciated. 
>
> 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 post to this group, send email to sympy@googlegroups.com.
Visit this group at https://groups.google.com/group/sympy.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sympy/d1f76e72-c2bd-4801-ab09-f3d94b0f2785%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [sympy] Re: Doing a release

2017-01-12 Thread Isuru Fernando

Same topic came up on sage-devel today with a solution.

https://groups.google.com/forum/m/#!topic/sage-devel/81qsOpoOKMM


Isuru Fernando

On Jan 12, 2017 5:30 AM, "Aaron Meurer"  wrote:

> So let's figure out how they do it. Does someone do it by hand, or do
> they just deal with the conflicts somehow?
>
> I'm +1 to doing this somehow, because the current process isn't
> working. We either need a process wherein everyone updates the release
> notes with their pull requests (has to be done at the same time or
> people won't do it), or just deal with release notes that are
> generated automatically (I believe this is what the IPython/Jupyter
> guys do).
>
> Aaron Meurer
>
> On Wed, Jan 11, 2017 at 4:55 PM, Jason Moore  wrote:
> > SciPy does it too: https://github.com/scipy/
> scipy/tree/master/doc/release
> > and the notes seem quite comprehensive and well organized.
> >
> > To avoid merge conflicts we could require a single file for each item in
> the
> > notes to be added and then a script compiles the full note set from
> those.
> >
> >
> > Jason
> > moorepants.info
> > +01 530-601-9791
> >
> > On Wed, Jan 11, 2017 at 10:20 AM, Aaron Meurer 
> wrote:
> >>
> >> Do you know how pandas generates those files? Are they generated
> >> programmatically or by hand? Usually having a single file for release
> >> notes gets to be a nightmare because of the merge conflicts.
> >>
> >> Aaron Meurer
> >>
> >> On Wed, Jan 11, 2017 at 1:46 AM, Shekhar Prasad Rajak
> >>  wrote:
> >> > I think, it will be easy during the new release to see the changes in
> >> > one
> >> > file, if we add a file in SymPy repo and keep updating it whenever
> >> > something
> >> > added/modified (Before merging PR). Something like this :
> >> > https://github.com/pandas-dev/pandas/tree/master/doc/source/whatsnew
> >> >
> >> > --
> >> > Shekhar
> >> >
> >> > On Monday, 26 September 2016 22:43:16 UTC+5:30, Aaron Meurer wrote:
> >> >>
> >> >> Now that GSoC has wrapped up, we should start looking at doing a
> >> >> release.
> >> >> As a start, can people
> >> >>
> >> >> - Mark issues and pull requests that need to be completed before the
> >> >> release with the "SymPy 1.1" milestone
> >> >>
> >> >> - Update the release notes with changes that have been merged
> >> >> https://github.com/sympy/sympy/wiki/Release-Notes-for-1.1
> >> >>
> >> >> Any help you can provide on the above two points (especially the
> >> >> release
> >> >> notes) would be greatly appreciated.
> >> >>
> >> >> 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 post to this group, send email to sympy@googlegroups.com.
> >> > Visit this group at https://groups.google.com/group/sympy.
> >> > To view this discussion on the web visit
> >> >
> >> > https://groups.google.com/d/msgid/sympy/a3f4a6c5-8a9c-
> 4560-b81b-0841323a8267%40googlegroups.com.
> >> >
> >> > For more options, visit https://groups.google.com/d/optout.
> >>
> >> --
> >> 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 post to this group, send email to sympy@googlegroups.com.
> >> Visit this group at https://groups.google.com/group/sympy.
> >> To view this discussion on the web visit
> >> https://groups.google.com/d/msgid/sympy/CAKgW%
> 3D6KnzE2nuGdmovQqs9UtDdPoZb-DHuAp2ReukURE2u8NKw%40mail.gmail.com.
> >> For more options, visit https://groups.google.com/d/optout.
> >
> >
> > --
> > 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 post to this group, send email to sympy@googlegroups.com.
> > Visit this group at https://groups.google.com/group/sympy.
> > To view this discussion on the web visit
> > https://groups.google.com/d/msgid/sympy/CAP7f1AiN4wzhTfXxg%
> 3DBqMyNR1ghCu-Ri_HWEvkX3RkWKmphrww%40mail.gmail.com.
> >
> > For more options, visit https://groups.google.com/d/optout.
>
> --
> 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 post to this group, send email to sympy@googlegroups.com.
> Visit this group at https://groups.google.com/group/sympy.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/sympy/CAKgW%3D6LsMT1DwqSym%3DSt-tWSumfYP5tC41o6eXa6_jPVs2k7jA%
> 40mail.gmail.com.
> For more options, visit

Re: [sympy] Re: Doing a release

[sympy] Re: SingularityFunction in sympy.physics.continuum_mechanics.beam

[sympy] Fwd: SingularityFunction in sympy.physics.continuum_mechanics.beam

[sympy] Re: Doing a release

Re: [sympy] Re: Doing a release

5 matches

Site Navigation

Mail list logo

Footer information