Stefan and Prasoon, could you comment on what you gather from that article? What I got was this - "A reference frame is essentially about a state of motion. Every reference frame can have various coordinate systems attached to it. These systems may be oriented (rotated and translated) in certain ways with respect to each other. If you want to define two *somethings* that differ in their state of motion with respect to each other, then the *something* must be a frame of reference. In a frame of reference, if you want a different *way* of _measuring_ things, then this *way* is a coordinate system. Hence, every coordinate system MUST be attached to a reference frame, without which its existence dosen't make sense. The only things that can be changed about frames and systems are their orientations and motion(only for frames) with respect to each other." Stefan, I would like your comments on this.
About a ScalarField class, it is just to - 1. Provide a structure similar to Vectors (so users can do something like- for x in list, print field.express(system)) 2. To ensure expression of the same field in different systems 3. To ensure field1 == field2 returns True if the fields are indeed equal (mathematically) -- 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 http://groups.google.com/group/sympy?hl=en-US. For more options, visit https://groups.google.com/groups/opt_out.
