Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

tree mesh -- to finalize or not? #269

Open
lheagy opened this issue Dec 5, 2021 · 0 comments
Open

tree mesh -- to finalize or not? #269

lheagy opened this issue Dec 5, 2021 · 0 comments
Labels
TreeMesh QuadTree or OcTree related

Comments

@lheagy
Copy link
Member

lheagy commented Dec 5, 2021

Currently, the implementations of utils for refining tree meshes are inconsistent with the default value for finalize

utils.refine_tree_xyz has a default value of False

def refine_tree_xyz(
mesh,
xyz,
method="radial",
octree_levels=[1, 1, 1],
octree_levels_padding=None,
finalize=False,
min_level=0,
max_distance=np.inf,
):

whereas mesh.refine_ball has a default True

def refine_ball(self, points, radii, levels, finalize=True):

which can be a source of confusion... I would vote for finalize=False as the default (at least in most use cases I have encountered, I am doing multiple refinement steps), but don't have overly strong opinions -- other than it would be useful if they were consistent.

And on a related note, there are no errors / warnings thrown if you try to refine a mesh that has already been finalized. So it might be worth a quick check & error if the mesh has already been finalized.

@lheagy lheagy added the TreeMesh QuadTree or OcTree related label Dec 6, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
TreeMesh QuadTree or OcTree related
Projects
None yet
Development

No branches or pull requests

1 participant