--
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+un...@googlegroups.com.
To post to this group, send email to sy...@googlegroups.com.
Visit this group at https://groups.google.com/group/sympy.
To view this discussion on the web visit https://groups.google.com/d/msgid/sympy/e2827c93-976c-496e-9c73-07aae4e2d1e0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
To view this discussion on the web visit https://groups.google.com/d/msgid/sympy/CALOxT-%3DfBwW4N16UE5esVGjM8hLBwbH8-TEMjpGkvXEa4UT0aA%40mail.gmail.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/sympy/CAP7f1AiVQVcnPfSt-Zhihc%2BsQt_NqJk4OhTbhVNCfi692pykkQ%40mail.gmail.com.
It's quite complicated to specify all these properties upon class creation, it would need lots of parameters.
Connecting a coordinate system to a Cartesian one fully specifies (mathematically) how the operators (gradient, divergence, curl) operate, but one could just wish to specify the form of the operators, without specifying the transformation function.
I believe an assumptions systems is a good way to handle coordinate systems. It could in principle also be extended to the matrix module.