Re: Notation related question

*To*: mathgroup at smc.vnet.net*Subject*: [mg72878] Re: [mg72841] Notation related question*From*: "T.Sariyski" <tsariysk at verizon.net>*Date*: Tue, 23 Jan 2007 05:46:35 -0500 (EST)*References*: <200701220839.DAA16705@smc.vnet.net>

Hi, I would like to build an environment for working on electrodynamics related problems using notations that mimics my writings on paper as closely as possible. Let say that there is a user defined type Vec so that E_Vec has internal representation {E_1,E_2,E_3}. Accordingly r_Vec would be represented internally as {r_1,r_2,r_3}. Than E[r] would be represented as {E_1[r_1,r_2,r_3],E_2[r_1,r_2,r_3],E_3[r_1,r_2,r_3]}. Assuming that the above construction is possible than a paper expression like div E(r) would be entered on the notebook as Div[E[r],Cartesian[r]]. I used to develop my code in Mathematica and generate Fortran code for production so that I would like to be able to: - formulate (exactly) a finite/infinite domain electrodynamic problem. - use DSolve or NDSolve (for simple test cases). - to generate Fortran formatted output (after proper discretization). Thanks, Ted Chris Chiasson wrote: > Could you maybe show us exactly how you intend to use these vectors? > That should make it easier to answer your questions, because your > current question does not make a lot of sense within the context of > how the front end and the kernel work. > > On 1/22/07, T.Sariyski <tsariysk at verizon.net> wrote: >> Hi, >> I want to make a function that takes an argument V and returns a list >> build of V with subscripts 1,2.3: V -> {V_1, V_2, V_3}. >> >> I symbolize V and define the function: >> >> Symbolize[NotationBoxTag[\(V\__\)]] >> Vec[V_]:={V_1, V_2, V_3}. >> >> It works as I expect for V but Vec[X] returns {V_1,V_2,V_3} instead of >> {X_1,X_2,X_3} as I expect. >> >> Anoter related (I think) question I have is how to define a _Vec type so >> that once I declare X_Vec the internal representation of X to be {X_1, >> X_2, X_3}? >> >> Thanks in advance, >> Ted >> >> >> >> > >

**References**:**Notation related question***From:*"T.Sariyski" <tsariysk@verizon.net>