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
Alan,
From what I can see in GA.py, you have one class MV, which doesn't
derive from anything, and then you use the setup method to somehow
inject MV objects into the global namespace. So, then, if x is a
sympy expression, and e is a MV object:
type(x*e) == type(e*x) ==
This is the sort of beh
We faced similar questions in sympy.physics.quantum. I think that all
mathematical objects should subclass Expr.
On Mon, May 9, 2011 at 4:23 PM, Gilbert Gede wrote:
> In PyDy (which we plan to merge into SymPy.physics.classical this summer)
> Vector is one of the classes already implemented (a
The assumption is that the expression multiplying the vector
(multivector) is a scalar and the
result is a vector. The geometric algebra is instantiated by defining a
set of abstract vectors
say e1, e2, e3, e4 and the dot product of all pairs of the vectors.
These dot products can be
symbols o
