comp.lang.idl-pvwave archive
Messages from Usenet group comp.lang.idl-pvwave, compiled by Paulo Penteado

Home » Public Forums » archive » Re: large 3D array plot
Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend 
Return to the default flat view Create a new topic Submit Reply
Re: large 3D array plot [message #49879 is a reply to message #49795] Fri, 18 August 2006 15:53 Go to previous messageGo to previous message
adisn123 is currently offline  adisn123
Messages: 44
Registered: July 2006
Member
> Another thing to consider would be to write your own viewer which HIDEs
> almost all of your data when you rotate the objects. You could do this
> by plotting the data in 2 IDLgrPolyline objects. One with some data,
> the other with lots. When a mousedown event is processed you hide the
> 'lots of data' polyline. At mouseup you unhide it. This probably would
> be an easy hack on XPLOT3D.

I'm not familiar with IDLgrPolyine objects. but, it seems like it draws
a line between
points, which I don't want to do.
What do you mean by "HIDEs almost all of your data when you rotate the
objects."?
How come you want to hide part of your date whilte rotating in 3D, then

what's the point of viewing in 3D?
Maybe, I didn't get what you meant...

THanks for the great tip on the symbols. I've never thought that'd be
an issue.





Rick Towler wrote:
> adisn123@yahoo.com wrote:
>> I'm using linux/unix with remote X.
>
> This is part of the issue. AFAIK, rendering while using remote X causes
> IDL to use the software renderer (but you'll want to verify this). That
> being said, even using the software renderer on my machine (3.6 GHz P4)
> I can view a cloud of 250k points reasonably well.
>
>
>> And, when I said "(3, 210,000)", I meant 3 columns and 210,000 rows,
>> thus 210,000 data points.
>> These points plot a galactic image(stars, galaxies, clouds,...)
>
> 200k vertices aren't much for modern hardware. Part of the problem is
> that these points are haphazardly arranged which will slow rendering. I
> can render a million vertex surface faster than a 250k vertex random
> "cloud" since the verts that form the surface are arrange in an optimal
> fashion.
>
>
>> I'm using symbols of spheres with linestyle = 6 thus, it does not
>> connect each individual point, but rather show as points of spheres.
>
> This compounds the issue immensely. Using spheres will add a large
> number of polygons to the scene thus slowing it down even further. If
> you followed the example for XPLOT3D, the default orb symbol has 402
> vertices so now you're rendering ~85 million verts!
>
> For this type of plot your approach (plotting a (hidden) line with
> symbols at the vertices) is probably the best way to go. Your real
> issue is the complexity of your symbol. Obviously you'll want to
> simplify it as much as possible. At the very least set the DENSITY
> keyword on your orb object to 0.2 which is the lowest you can set it to
> and still have a 3d object (it has 18 vertices). The simplest symbol you
> can get away with will be a tetrahedron (4 verts):
>
> nverts = 210000
> seed = SYSTIME(/SECONDS)
> xyz = RANDOMU(seed, 3, nverts) * 1000
>
> oTetra = OBJ_NEW('RHTgrPSolid', /TETRAHEDRON, $
> RADIUS=0.2, COLOR=[75,125,230])
> oTetra -> GetProperty, OBJECT=pObj
> oSym = OBJ_NEW('IDLgrSymbol', pObj)
>
> XPLOT3D, xyz[0,*], xyz[1,*], xyz[2,*], SYMBOL=oSym, $
> LINESTYLE=6, /BLOCK
>
> OBJ_DESTROY, [oTetra, oSym]
>
> You can make your own tetrahedron or get RHTgrPSolid at:
> http://www.acoustics.washington.edu/~towler/programs/rhtgrps olid__define.pro
>
>
> Another thing to consider would be to write your own viewer which HIDEs
> almost all of your data when you rotate the objects. You could do this
> by plotting the data in 2 IDLgrPolyline objects. One with some data,
> the other with lots. When a mousedown event is processed you hide the
> 'lots of data' polyline. At mouseup you unhide it. This probably would
> be an easy hack on XPLOT3D.
>
>
>> I'm not sure what graphics card installed on my machine.
>
> No need to check at this point, but if simplifying your symbol doesn't
> speed things up as much as you need, you may want to consider writing a
> program to plot your data that will work with the IDL VM and install
> that on your local machine. There still will be issues of configuring X
> to use hardware rendering which can be easy or hard but at least you'll
> have a better chance of viewing this data interactively.
>
>
> -Rick
[Message index]
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: Re: Algorithm for lat/lon searching
Next Topic: Re: oplot for plots

-=] Back to Top [=-
[ Syndicate this forum (XML) ] [ RSS ] [ PDF ]

Current Time: Fri Oct 10 14:05:10 PDT 2025

Total time taken to generate the page: 0.96335 seconds