From e797f0e48d0e98ce09771eb2d7e37a1f8a770865 Mon Sep 17 00:00:00 2001 From: Alex Matulich Date: Mon, 24 Mar 2025 17:39:44 -0700 Subject: [PATCH] minor copyedits --- isosurface.scad | 9 ++++----- 1 file changed, 4 insertions(+), 5 deletions(-) diff --git a/isosurface.scad b/isosurface.scad index 612d2d8..aa91e29 100644 --- a/isosurface.scad +++ b/isosurface.scad @@ -3259,7 +3259,7 @@ function _metaballs2dfield(funclist, transmatrix, bbox, pixsize, nballs) = let( // (x*y*z^3 - 3*x^2*z^2) / np^2 + np^2, // isovalue=[-INF,35], bounding_box=[[-32,-32,-14],[32,32,14]], // voxel_size = 0.8, show_box=true); -// Example(3D,Med,NoAxes,VPD=47,VPT=[0,0,2]): You can specify non-cubical voxels for efficiency. This example shows the result of two identical surface functions. The figure on the left uses a `voxel_size=1`, which washes out the detail in the z direction. The figure on the right shows the same shape with `voxel_size=[0.5,1,0.2]` to give a bit more resolution in the x direction and much more resolution in the z direction. This example runs about six times faster than if we used a cubical voxel of size 0.2 to capture the detail in only one axis at the expense of unnecessary detail in other axes. +// Example(3D,Med,NoAxes,VPD=47,VPT=[0,0,2]): You can specify non-cubical voxels for efficiency. This example shows the result of two identical surface functions. The figure on the left uses `voxel_size=1`, which washes out the detail in the z direction. The figure on the right shows the same shape with `voxel_size=[0.5,1,0.2]` to give a bit more resolution in the x direction and much more resolution in the z direction. This example runs about six times faster than if we used a cubical voxel of size 0.2 to capture the detail in only one axis at the expense of unnecessary detail in other axes. // function shape(x,y,z, r=5) = // r / sqrt(x^2 + 0.5*(y^2 + z^2) + 0.5*r*cos(200*z)); // bbox = [[-6,-8,0], [6,8,7]]; @@ -3480,10 +3480,9 @@ function _showstats_isosurface(voxsize, bbox, isoval, cubes, triangles, faces) = // means that the list of paths may include a mixture of closed and open paths. Regardless of whether // any of the output paths are open, all closed paths have identical first and last points so that closed and // open paths can be distinguished. You can use {{are_ends_equal()}} to determine if a path is closed. A path -// list that includes open paths is not a region, since regions are lists of closed polygons. Duplicating the -// ends of closed paths can cause problems for some functions such as {{offset()}} which will complain about -// repeated points; to deal with this problem you can pass the closed components to {{list_unwrap()}} to remove -// the extra endpoint. +// list that includes open paths is not a region, because regions are lists of closed polygons. Duplicating the +// ends of closed paths can cause problems for functions such as {{offset()}}, which would complain about +// repeated points. You can pass a closed path to {{list_unwrap()}} to remove the extra endpoint. // Arguments: // f = The contour function or array. // isovalue = a scalar giving the isovalue parameter.