Chris, Thanks much for the rapid reply. I was just in the process of putting things into a group (hoping that DX would prefer the data in one big conglomerate object) when I got your e-mail.
For simplicity I put every array in the data file into a field and then made a group of the fields in the data header file. So, import sees a group containing the fields, Density, Pressure, Vx, Vy, Vz, Bx, By, Bz. Then as you suggested I used a "selector interactor" in combination with "select" to strip of the desired field. This works great. Add autocolor and image and I'm a long way ahead. Additionally, with a 6 "selects" and 2 "computes" I now have the velocity and magnetic field vectors (Describe is a nice tool for getting this to work!) Before I ask for more help, let me just say that if you've no time, or the details are getting too nitty gritty, then I'd be more than happy with any reference to sections of the userguide, exemplary samples, or pointers. I don't want to step on you "consulting" toes, so to speak. With that said, sometimes I'd like to visualize the cylindrically symmetric data in the (r,z) plane and sometimes I'd like to see it rotated. For that reason does it make more sense to describe the rotation in the connections part of the header file or with your trick in the DX network? You wrote: On Mon, 19 Jun 2000, Chris Pelkie wrote: > >Right: points is points, connections is connections. If the connections >happen to form a ring, so be it. That could be done in your definition of >the connections, though there are ways to do it within DX (however, there >are some "special" rules that become involved with vector fields: here the >dimensionality may matter, of the vectors and of the space; let's delay >that discussion until you hit the problem). Put it this way: you can fairly >trivially warp the flat mesh into a cylinder. Joining it toroidally within >DX is not too hard either, though there is a trick involved. I'll wait til >you need to know the trick. I'd also like to view animations of say the density made up from the density spread over many data files. My first thought on doing this is to create a separate header file which describes a series object and refers to say the density fields in the header files for each individual data dump. Will this work? Any better ideas? I'd like to cover all of the bases, though I'm beginning to wonder if I'm gonna end up writing a ton of header files. My last question I can think of right now is how I might overlay vectors indicating the velocity or magnetic field orientations on top of say density. I remember seeing something like this in the samples, so I'm going there after I finnish this e-mail. Any suggestions? Thanks Much, Tom
