🚀 go-pugleaf

I am trying to look at a very large data set (164,344 nodes) representing
fuel concentrations in a pulp boiler. The data consists of 9 "zones",
stacked horizontally, each of which is a perimeter lattice, with
lattice dimensions varying from zone to zone.

I have read the first 3 zones into perimeter lattices, and can slice them
individually using OrthoSlice. I have also tried reading them in as
curvilinear lattices and slicing them with ProbeLat. This is okay, except
I don't really understand how the Transform Input to ProbeLat works.

Anyway, what I *really* want to do is have a single slicer
(or several syncronized slicers) slice through the entire data set,
based on the coordinates of the slicer and showing the resolution of 
each of the lattices that make up the data.

I thought about converting the data set to a pyramid lattice, but I 
don't think our 32Meg machine could handle it.

Any ideas? Am I missing something obvious?

Helen Salter, Visualization Support, Computing Services
University of British Columbia, B.C. Canada.


Newsgroups: comp.graphics.explorer
Subject: Synchronized slicing of multiple lattices
Summary: 
Expires: 
References:
Sender: Helen Salter
Followup-To: 
Distribution: 
Organization: University of B.C. Computing Services
Keywords: OrthoSlice ProbeLat Curvilinear

I am trying to look at a very large data set (164,344 nodes) representing
fuel concentrations in a pulp boiler. The data consists of 9 "zones",
stacked horizontally, each of which is a perimeter lattice, with
lattice resolution varying from zone to zone.

I have read the first 3 zones into perimeter lattices, and can slice them
individually using OrthoSlice. I have also tried reading them in as
curvilinear lattices and slicing them with ProbeLat. This is okay, except
I don't really understand how the Transform Input to ProbeLat works.

Anyway, what I *really* want to be able to do is have a single slicer
(or several syncronized slicers) slice through the entire data set,
based on the coordinates of the slicer and showing the resolution of 
each of the lattices that make up the data.

I thought about converting the data set to a pyramid lattice, but I 
don't think our 32Meg machine could handle it.

Any ideas? Am I missing something obvious?

Helen Salter, Visualization Support, Computing Services
University of British Columbia, B.C. Canada.




-- 
Helen Salter; salter@ucs.ubc.ca; 
Visualization Support, Computing Services;
University of British Columbia, Canada