Conversation
Greptile OverviewGreptile SummaryThis PR adds an experimental Key merge blockers are: (1) the changelog entry points at the wrong import path ( Important Files Changed
|
Additional Comments (1)
|
|
@coreyjadams could you review this new |
|
Depends on #1362 for CI to pass. |
|
/blossom-ci |
|
/blossom-ci |
|
/blossom-ci |
|
/blossom-ci |
|
@ktangsali thanks for reviewing this PR and for your great comments! All of your comments are addressed, please re-review. The most concerning comment for me was the potential bug in handling STLs with multiple solids. I verified that pyvista merges multi-solid STLs into a single mesh when loading, so that is not an issue. |
|
/blossom-ci |
|
/blossom-ci |
|
/blossom-ci |
ktangsali
left a comment
There was a problem hiding this comment.
Looks good! Thanks for addressing my comments. Approved with only a minor follow up on previous comment.
PhysicsNeMo Pull Request
Description
This PR introduces a new experimental module (
physicsnemo.experimental.guardrails) for detecting out-of-distribution geometric configurations in CAD models and simulation meshes using density-based anomaly detection. The module extracts 22 non-invariant geometric features (centroid, PCA axes/eigenvalues, bounding box, surface areas) and supports two density estimation methods: Gaussian Mixture Models (GMM) with optional GPU acceleration, and Polynomial Chaos Expansion (PCE) using Hermite polynomials (currently CPU only). Key features include parallel STL loading with multiprocessing, optional Rust-based fast I/O adapter, three-level classification (OK/WARN/REJECT) based on empirical percentiles, production-ready serialization with automatic schema versioning, and comprehensive tests and documentation. The API is simple (GeometryGuardrail.fit(meshes)/.query(meshes)), and handles optional dependencies gracefully (Rust reader).Checklist
Dependencies
Review Process
All PRs are reviewed by the PhysicsNeMo team before merging.
Depending on which files are changed, GitHub may automatically assign a maintainer for review.
We are also testing AI-based code review tools (e.g., Greptile), which may add automated comments with a confidence score.
This score reflects the AI’s assessment of merge readiness and is not a qualitative judgment of your work, nor is
it an indication that the PR will be accepted / rejected.
AI-generated feedback should be reviewed critically for usefulness.
You are not required to respond to every AI comment, but they are intended to help both authors and reviewers.
Please react to Greptile comments with 👍 or 👎 to provide feedback on their accuracy.