star-vx

Structuring voxels for ray-tracing
git clone git://git.meso-star.fr/star-vx.git
Log | Files | Refs | README | LICENSE

commit e44b9bd5c7b2553b6966d9098620fb61b07e63dc
parent c8be87dd616e3d4b360def60888945a5f4389e4f
Author: Vincent Forest <vincent.forest@meso-star.com>
Date:   Wed,  4 Jan 2023 14:20:03 +0100

Minor update of the overview section in the README

Diffstat:
MREADME.md | 2+-
1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/README.md b/README.md @@ -10,7 +10,7 @@ to access them through ray-tracing. Star-VX proposes 2 hierarchical data structures: the *octree* and the *binary tree*. The first one is used to structure regular 3D data while the second one is for 1D data. Star-VX build the required data structure following a -bottom-top strategy: the user submits the set of data to partition as well as +bottom-up strategy: the user submits the set of data to partition as well as the policy used to define when voxels can be merged and the merge operator itself. The way data are accessed through *indexing* or *ray-tracing* can also be finely tuned by the user. In addition of the probe position or the ray to