On Sun, May 15, 2011 at 1:40 AM, Luke wrote:
> Gilbert,
> I prefer this notation:
>
B = ReferenceFrame('B')
>
> and then to access the basic vectors of that frame, to use one of the
> following approaches:
>
> B.x, B.y, B.z or, B.i, B.j, B.k
>
> You could view the ReferenceFrame class as a c
Gilbert,
I prefer this notation:
>>> B = ReferenceFrame('B')
and then to access the basic vectors of that frame, to use one of the
following approaches:
B.x, B.y, B.z or, B.i, B.j, B.k
You could view the ReferenceFrame class as a container object for the
basis vectors and implement the __iter
So I think we've decided to make a new Vector class, to replace the
previous UnitVector and Vector classes, and it will not extend any
other sympy classes. It will use sympy's matrix class. The current
plan is for each vector to have a list of lists; the inner list will
be the coefficients of eac
Le mardi 10 mai 2011 à 11:37 -0700, Luke a écrit :
> The dot and cross products are implemented at the lowest level in
> UnitVector, and the Vector class simply calls these methods on all of
> the UnitVector objects that comprise it when these methods are called
> on a Vector class.
>
> dot and cr
The dot and cross products are implemented at the lowest level in
UnitVector, and the Vector class simply calls these methods on all of
the UnitVector objects that comprise it when these methods are called
on a Vector class.
dot and cross functions are provided as convenience wrapper functions
aro
On 10 Mai, 03:30, Ronan Lamy wrote:
> Please, try to make the interface dot(v1, v2), and not v1.dot(v2).
While I agree that it looks cleaner for the simple case, I would
prefer
v1.dot(v2).dot(v3)
over
dot(dot(v1, v2), v3)
For the dot product it does of course not make sense to multipl
