>I love DX, people here at my department think I'm a god! Must be nice. I've begged them to worship me around here and nothing, nada. (:-)
> >Regarding you comment to the other suggestion, I'm also very interested >in memory optmization, even though the meshes I'm working with are >a lot smaller than yours (about 60000 nodes, 250000 elements). It's >funny to see how quicky and gladly DX takes up 200MBytes. I still have some >left, but in the near future intend to work with larger meshes, so memory >is an issue to me. > Precisely because DX requires gobs of memory, you need to keep in mind the memory allocation that goes on under the covers, thus I hope my analysis raises awareness of how to avoid making really unnecessary arrays when possible. Often it's unavoidable, so other strategies are needed but in this case, the last solution I provided in my second note is probably the most parsimonious to accomplish the task. Chris Pelkie Vice President/Scientific Visualization Producer Conceptual Reality Presentations, Inc. 30 West Meadow Drive Ithaca, NY 14850 [EMAIL PROTECTED]
