If the data is 'columnized', DX format is less useful cause you'd have to do many annoying restructuring ops in the net. General format excels there, I admit.
Maybe you can use Stack to raise the dimensionality of your flat object. Just a thought (read the Stack doco).
On May 23, 2005, at 11:24 AM, Matthew Bogosian wrote:
-----BEGIN PGP SIGNED MESSAGE-----_______________________________
Hash: SHA1
Hmmm...I was hoping that wasn't the case. I'm exporting data from the source to multiple different "analysis" programs (one of which is OpenDX), and I was hoping to keep the base file as generic as possible. Does the DX data format have a provision for raw data that exists elsewhere?
-- Matt
On May 20, 2005, at 14:13, Chris Pelkie wrote:
Re dimensions question: if you were to Construct a grid 2x1, you would get a 1-D line; if you specified 3-vector origin, you'd nevertheless have 3-D positions. 2x2 would give a 2-D quad. Ergo, I x J x K x 1 yields 3-D not 4-D connections.
You should be looking at the DX data format (methinks you're outgrowing the general format with the sophistication of your data objects). You could then attach an attribute (for example) to a field to flag the fact that the 4th dimension is only 1 thick in those cases where it is, and have an Attribute fetch that value to throw a Switch in the net to properly deal with that instance vs. a "fat" 4th dimension instance. There's no way to add such 'advanced' capability to general files (or if there is, I don't care, cause I wouldn't waste time trying to force it to do what DX format does so much more elegantly).
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (Darwin)
iD8DBQFCkfWQnLpDzL5I7l8RAkwjAJ9iLs9K7Nlst+8T3rQeRa7VI7dy3wCfV16N
k9rODu1YEAuKP7kXCckHuO4=
=z6jd
-----END PGP SIGNATURE-----
Chris Pelkie
Scientific Visualization Producer
622 Rhodes Hall, Cornell Theory Center
Ithaca, NY 14853 (607) 254-8794
