NOTICE: This version of the NSF Unidata web site (archive.unidata.ucar.edu) is no longer being updated.
Current content can be found at unidata.ucar.edu.
To learn about what's going on, see About the Archive Site.
NOTICE: This version of the NSF Unidata web site (archive.unidata.ucar.edu) is no longer being updated.
Current content can be found at unidata.ucar.edu.
To learn about what's going on, see About the Archive Site.
I ran into the same when developing my software. My solution is to resample the data to a cubic resolution. I've found that cubes larger than 128 x 128 x 128 simply take too much memory, so my application caps things there. In your case, I'd suggest resampling to 32 x 32 x 32 and 61 x 61 x 61, respectively. Of course, it will use more memory, but things will look much smoother. As for the aspect ratio, I haven't experimented with that, but my guess is that it will not solve your problem. If you try it, though, feel free to share your experiences. -Curtis At 02:44 PM 2/13/2003, you wrote: >Curtis: > >As a matter of fact, the z face does indeed have fewer samples--one data file >is 32 x 32 x 16 and the other is 61 x 61 x 5. >If I set the aspect ratio of the display to better match the sampling, will >VisAD do a better job with the volume rendering? Thanks! > >oz > >Curtis Rueden wrote: >> >>Hi John, >> >>Do your volume's samples form a cube (e.g., 64 x 64 x 64), >>or does the z-face have fewer samples? VisAD's volume >>rendering performs less well with uneven sample lengths, >>such as 512 x 512 x 5. >> >>-Curtis
visad archives: