AcademySoftwareFoundation / AcademySoftwareFoundation/openvdb

openvdb::tools::meshToSignedDistanceField does not support anisotrop voxel sizes

Open
#151 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
C++
Stars
3.4k
Forks
774
Avg merge
3d 9h
Merged PRs (30d)
34

Description

I tried using meshToSignedDistanceField with a world to index transform that maps to
an anisotrop voxel size (e.g. 0.5, 0.25, 0.25). When reading the resulting distance field,
I noticed that the distances are wrong, because only the voxel size in X dimension is taken into account:

`const ValueType voxelSize = ValueType(transform.voxelSize()[0]);
`
Could you maybe support anisotropic voxel sizes in a future version?

Contributor guide

Open the contributing guide

Research direction

Start at the meshToSignedDistanceField entry point and inspect the reported voxelSize use, especially the conversion that reads only the X dimension. Confirm the distance field remains correct when the world-to-index transform has different voxel sizes on each axis, then verify the relevant existing tests or add coverage for the anisotropic example.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
computer-graphics
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.