Add surface meshing parameters to Poisson surface reconstruction

[Copilot]

• Review CGAL documentation for available Poisson reconstruction parameters
• Update C++ implementation to accept optional parameters (sm_angle, sm_radius, sm_distance)
• Update C++ header file with new function signature
• Update Python wrapper to accept and pass through new parameters with sensible defaults
• Update docstrings in Python to document new parameters
• Create/update tests to verify new parameters work correctly
• Update example code to demonstrate parameter usage
• Apply code formatting with black
• Address code review feedback (refactor tests)
• Run security checks (no issues found)
• Update CHANGELOG.md

Summary

Successfully implemented support for additional parameter inputs for Poisson Surface Reconstruction:

Added Parameters:

1. sm_angle (default: 20.0): Surface meshing angle bound in degrees - controls minimum angle of triangles
2. sm_radius (default: 30.0): Surface meshing radius bound - controls triangle size relative to point cloud density
3. sm_distance (default: 0.375): Surface meshing approximation error bound - controls mesh fidelity

Key Features:

• All parameters have sensible defaults matching CGAL's recommendations
• Backward compatible - existing code continues to work without changes
• Comprehensive documentation with usage examples
• Tested with multiple parameter combinations
• Code passes all linters and security checks
• CHANGELOG.md updated

Benefits:

Users can now control mesh quality and density to filter out vertices that don't belong to the original point cloud by adjusting sm_radius and sm_distance parameters, directly addressing the issue request.

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Support for additional parameter inputs for Poisson Surface Reconstruction</issue_title>
<issue_description>Thank you for the excellent work!

Feature Request

As a designer, I want additional parameter inputs for Poisson Surface Reconstruction so that I can have more control over the generated mesh.

Details

Is your feature request related to a problem? Please describe.
The generated mesh has too many mesh vertices that do not belong to the original point cloud.

Describe the solution you'd like
There should be a parameter to filter the vertices. Like the CockRoach plugin in Rhino using "isovalue" orthe Grasshopper plugin using "density".

Appreciate your contribution again!
</issue_description>

<agent_instructions>explore passing parameters to poisson surface reconstruction</agent_instructions>

Comments on the Issue (you are @copilot in this section)

@tomvanmele @petrasvestartas

• Fixes Support for additional parameter inputs for Poisson Surface Reconstruction #53

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[jf---]

@copilot update the changelog.md

[Copilot]

@copilot update the changelog.md

Updated CHANGELOG.md in commit c4ab4ce with an entry documenting the new surface meshing parameters added to poisson_surface_reconstruction.

[jf---]

wait for merging of other PR's, than we need to rebase this PR

[petrasvestartas]

Let's merge them one by one, so that there would be no conflicts.

[jf---]

super clean, uses the Eigen::Ref<const compas::RowMatrixXd>.
@petrasvestartas this PR is not related to pending PR's so can be merged.

[jf---]

I guess updating the docs where changes in the reconstruction parameters are shown is relevant.

[tomvanmele]

i have integrated everything in the new mkdocs setup
https://compas.dev/compas_cgal/examples/example_geodesics/

there is a bit more cleaning up to do, but getting there...

[jf---]

there is a bit more cleaning up to do, but getting there...

wow, looks great!