Stefan,
I think I disagree about Reference Frames being immutable. If you are going
to create a series of Reference Frames when performing successive
rotations, you are going to need to need to be able to modify the original
frame to point to the new frames. There is a similar issue for setting the
> @Stefan. I agree about the tree traversals part. However, I still feel there
> must be a way for the user to check if two scalar fields expressed in
> different ways are mathematically equivalent. Could you suggest a way? Maybe
> just another function?
This is described in one of the first pa
@Stefan. I agree about the tree traversals part. However, I still feel
there must be a way for the user to check if two scalar fields expressed in
different ways are mathematically equivalent. Could you suggest a way?
Maybe just another function?
Also, have a look at the __eq__ function of the curr
@Gilbert
> If you have the same scalar field, written in a rectangular coordinate
system as x * y * z and in a spherical coordinate system as
r*sin(theta)*cos(phi) * r*sin(theta)*sin(phi) * r*cos(theta), and these two
coordinate systems have the same orientation and origin, the scalar fields
shoul
+1.
I added one or two comments, they are mostly just clarifications. But I
guess we agree on the basics now.
I will post some hand-written scanned stuff about the math of Stefan's
stress test on my blog in a day, mainly to clarify things in my own mind as
well.
Prasoon, could you expand on the con
I have made some comments on the wiki. Let us get the API decided so that
both I and Sachin can get started with some work. Thanks.
--
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
