Hi all,
I forgot to mention this earlier. I think PR 2344
(https://github.com/sympy/sympy/pull/2344) is ready to be merged. It
passes all tests.
On Sunday, 4 August 2013 23:15:39 UTC+1, Aaron Meurer wrote:
>
> Returning a string is much better. If you want to do anything with the
> string (
Returning a string is much better. If you want to do anything with the
string (including print it), you can do it if you return the string.
But if you print the string, you can't do anything with it.
I wouldn't include a newline at the end. The other SymPy printers do
not do this. It will just res
On Sun, Aug 4, 2013 at 10:06 AM, Mary Clark wrote:
> David: The dynkin_diagram method does return a string. However, it has a
> newline character in it, so you need a print statement to make things show
> up in two lines, rather than one line with a "\n".
>
Okay. In that case, what I often do is
David: The dynkin_diagram method does return a string. However, it has a
newline character in it, so you need a print statement to make things show
up in two lines, rather than one line with a "\n".
On Friday, 2 August 2013 22:33:04 UTC+1, David Joyner wrote:
>
>
>
> On Friday, August 2, 2013,
On Friday, August 2, 2013, Mary Clark wrote:
> Additionally, regarding PR 2344, in my docstring for dynkin_diagram.py I
> have a print statement:
>
> >>> print DynkinDiagram("A3")
> 0---0---0
> 1 2 3
>
> Now, I just found out how in python 3.x print is now a function, so you
> need pr
Matthew, that did solve things! Thank you so much!
Speaking of which, here is the travis build:
https://travis-ci.org/sympy/sympy/builds/9662620
I think that things are good to merge now?
On Tuesday, 30 July 2013 20:01:34 UTC+1, Mary Clark wrote:
>
> Thanks Matthew, I shall try that.
>
> On Tue
Thanks Matthew, I shall try that.
On Tuesday, 30 July 2013 19:26:36 UTC+1, Matthew Brett wrote:
>
> Hi,
>
> On Tue, Jul 30, 2013 at 11:13 AM, David Joyner
> >
> wrote:
> >
> >
> > On Tuesday, July 30, 2013, Mary Clark wrote:
> >>
> >> So I've been fixing things to merge with master, and I
Hi,
On Tue, Jul 30, 2013 at 11:13 AM, David Joyner wrote:
>
>
> On Tuesday, July 30, 2013, Mary Clark wrote:
>>
>> So I've been fixing things to merge with master, and I am a bit confused
>> about some errors that the travis build is giving me.
>> Here is the link to the travis build:
>> https://
On Tuesday, July 30, 2013, Mary Clark wrote:
> So I've been fixing things to merge with master, and I am a bit confused
> about some errors that the travis build is giving me.
> Here is the link to the travis build:
> https://travis-ci.org/sympy/sympy/builds/9653672
>
> I am uncertain as to why th
Thanks, David! I was scanning that document earlier, but I missed that
part. That should definitely help.
On Wednesday, 19 June 2013 21:14:03 UTC+1, David Joyner wrote:
>
> On Wed, Jun 19, 2013 at 3:53 PM, Mary Clark
> >
> wrote:
> >
> >> Just a question on terminology:
> >> Are you talkin
I'm unfortunately ignorant of the commutation relations of su(2) and su(3)
but I am generally interested in the clear expression of mathematics in
code. Are you able to either point to simple and quick-to-read reference
or give a clear example of the problem and the importance (I prefer the
latter
On Wed, Jun 19, 2013 at 3:53 PM, Mary Clark wrote:
>
>> Just a question on terminology:
>> Are you talking about general commutation relations or just those for the
>> standard lie algebra generators?
>
>
> Sorry, but could you clarify what you mean? For instance, what I'm saying
> is that su(2),
> Just a question on terminology:
> Are you talking about general commutation relations or just those for the
> standard lie algebra generators?
Sorry, but could you clarify what you mean? For instance, what I'm saying
is that su(2), for example, has a basis consisting of 3 elements, say u1
On Wed, Jun 19, 2013 at 3:31 PM, Mary Clark wrote:
> Hello all,
>
> As we all know, this is the first week of GSOC and I'm working on a Lie
> algebra module. My blog is http://meclark256.wordpress.com/
>
> Specifically I'd like to generate some discussion on the issue that I just
> wrote about in
Hello all,
As we all know, this is the first week of GSOC and I'm working on a Lie
algebra module. My blog is http://meclark256.wordpress.com/
Specifically I'd like to generate some discussion on the issue that I just
wrote about in this week's blog entry, on actual physical commutation
rela
On Friday, 5 April 2013 13:26:56 UTC+1, Matthew wrote:
>
> I know nothing about Lie Algebras (well, maybe I could make a loose
> definition). From an outsider's perspective I'd like to know the
> following. These questions are general to any project. They reflect my
> personal interests, no
I know nothing about Lie Algebras (well, maybe I could make a loose
definition). From an outsider's perspective I'd like to know the
following. These questions are general to any project. They reflect my
personal interests, not necessarily the interests of the community
1. What is the computat
On Friday, 5 April 2013 01:26:10 UTC+1, David Joyner wrote:
>
> A couple of questions:
> How would you represent the Weyl gp? As a permutation group?
>
Yes, as a permutation group. They are most easily expressed this way; for
example the Weyl group of sln is just Sn, and for the other exceptio
A couple of questions:
How would you represent the Weyl gp? As a permutation group?
How would you represent an element of a root system? As both
a dict or a vector (or just one or the other)?
Would you implement a group action on the root lattice?
Would you implement a Lie algebra as a vector space
Hello all,
I've been working on and thinking about my proposal for a Lie Algebra
module.Ideally I'd like to have the following classes:
- Cartan Type (eg A4, B3, etc)
- subclasses would implement Dynkin diagrams and the Cartan matrix
- also include functions to return the ran
20 matches
Mail list logo
