Re: [Algorithms] PVA hierarchies (was: Terrain performance etc)

[Jonathan B. <jo...@nu...>]

> The dataset I mention is available to the public, in the sense
> that it has been approved for release.  It is too big to
> put on the little servers we have accessible to the public, however,
> at least for all the timesteps (total data is 274*2048*2048*1920
> bytes, i.e. 2.4 terabytes).  A single timestep gzips
> down to about 2 gig.  I'll see if I can get that on
> our web site.  I can ftp to whoever asks, but I can't
> handle a lot of requests by hand like that. 

Some 2 gig files, I can put on my server.  2.4TB is too much
for me though.  So if you can ftp me an interesting frame or two,
I will make a little web page that exports the data to everyone.
I'll talk to you off-list about the ftp.

>  The easiest thing to hand out (size-wise)
> is the raw brick of field data and some code to
> extract an isocontour surface.  

> The surfaces end up bigger that the original brick data!  

Not too surprising.  I think everyone is realizing that triangle meshes
are actually somewhat inefficient for high-res data, not that anyone
has a clearly better idea though.

  -Jonathan.