Humanoid PointClouds
Towards bringing together the gallery project and CITRIS's tele-immersion lab, we've taken some data from Sang-Hack Jung and imported it into croquet.
The data is simply lots and lots of points with XYZ & RGB info.
Each frame is approximate 150,000 points, with a framerate of about 12Hz.
Below are preliminary results showing simply getting some of the data in to Croquet.
Next steps are reading in approximately 50 frames from 50 files,
followed hopefully by networking.
Qualitative observations:
The data reads in from disk nigh instantly via AsyncFile, straight into a B3DVector3Array.
Additionally it scales quite fast, which surprised me because the actual points are scaled rather than having the scale in the matrix.
Very slow however is computing the bounding sphere/box of the cloud.
I'll probably pre-calculate this and include it in the data files.
The data is simply lots and lots of points with XYZ & RGB info.
Each frame is approximate 150,000 points, with a framerate of about 12Hz.
Below are preliminary results showing simply getting some of the data in to Croquet.
Next steps are reading in approximately 50 frames from 50 files,
followed hopefully by networking.
Qualitative observations:
The data reads in from disk nigh instantly via AsyncFile, straight into a B3DVector3Array.
Additionally it scales quite fast, which surprised me because the actual points are scaled rather than having the scale in the matrix.
Very slow however is computing the bounding sphere/box of the cloud.
I'll probably pre-calculate this and include it in the data files.
posted by orion at 4:12 PM
2 Comments:
Why not keep a max/min tally while inputing
points?
Although, this will still eat up cycles.
By putting boundary information in the
file it may allow easier use of relative coordinates, compression, and maybe lossy
input if needed, so I think this is best.
tallying the points as their read in (or after, since they're read in in bulk) would certainly work, but with 100,000 points it takes several seconds on a relatively fast computer.
reading the file in bulk into memory is much, much faster than processing it.
lossy input - good idea!
Post a Comment
<< Home