← Back to AI Insights
Gemini Executive Synthesis

usd-brep library, specifically occt_to_usd conversion for NURBS-based boundary representation (BRep) solid modeling, with a focus on accurate area calculation for complex geometries.

Technical Positioning
Accurate geometric representation and conversion for CAD/BRep data within the USD ecosystem. The goal is precise area calculation, which is failing to converge with increased accuracy settings.
SaaS Insight & Market Implications
This issue reveals a critical precision failure in `usd-brep`'s `occt_to_usd` conversion, specifically for complex B-spline geometry. A 0.65% area error that plateaus despite increased `relative_accuracy` indicates a fundamental algorithmic or implementation flaw, not a simple precision limit. This directly impacts the reliability of USD for industrial CAD workflows, particularly with vendor-supplied STEP models containing rational B-splines. The inability to achieve convergence on a basic geometric property like area undermines trust in the library's foundational accuracy, posing a significant barrier to adoption in engineering and manufacturing sectors where precise geometric fidelity is non-negotiable. The explicit non-applicability of existing workarounds suggests a novel or more complex defect requiring deeper investigation.
Proprietary Technical Taxonomy
USD BRep NURBS-based boundary representation (BRep) solid modeling occt_to_usd planar face rational B-spline edges Face.area() relative_accuracy plateaus

Raw Developer Origin & Technical Request

Source Icon GitHub Issue Oct 16, 2026
Repo: NVIDIA-Omniverse/usd-brep
occt_to_usd: planar face with rational B-spline edges imports ~0.65% too large; Face.area() error plateaus instead of converging

### Summary

A single planar face imported with `occt_to_usd` comes back from `usd_brep` with an area about **0.65% too large**, and the error does **not** go away as `relative_accuracy` is tightened: it plateaus at +0.6525% from 1e-6 down to 1e-12. KNOWN_ISSUES.md ("Area, volume and mass properties of faces bounded by circles") says the error falls as the accuracy is tightened; here it stops falling well above zero, so that workaround does not apply.

The face's 3D boundary survives the round trip exactly. The extra area comes from the region SMLib treats as inside the trim.

### Environment

- usd-brep `c9c5979` (main, 2026-10-09), Windows 11, release build (VS 2022 Build Tools, v143 toolset)
- Input `.brep` written by OCCT 8.0 (via `cadquery-ocp` 8.0.1) in ASCII format V3

### Face

One planar face with one loop of 6 edges, all B-spline curves. The two long edges are rational with interior knots (weights around 0.9997 to 0.99985). The face comes from a vendor STEP model of a pre-cambered steel member. It was translated so its bbox min corner sits at the origin, and the error is the same before and after the translation.

### Reproduce

```
occt_to_usd face3149.brep face3149.usda
```

```python
import usd_brep.usd as ubu
face = ubu.import_breps("face3149.usda")[0].faces()[0]
for acc in (1e-1, 1e-3, 1e-6, 1e-9, 1e-12):
print(acc, face.area(acc))
```

### Measured

| Method | Area | vs reference |
|---|---|---|
| Reference: vector area of the closed boundary polyline (Gre...

Developer Debate & Comments

No active discussions extracted for this entry yet.

Adjacent Repository Pain Points

Other highly discussed features and pain points extracted from NVIDIA-Omniverse/usd-brep.

Frequently Asked Questions

Market intelligence mapped to usd-brep library, specifically occt_to_usd conversion for NURBS-based boundary representation (BRep) solid modeling, with a focus on accurate area calculation for complex geometries..

How is usd-brep library, specifically occt_to_usd conversion for NURBS-based boundary representation (BRep) solid modeling, with a focus on accurate area calculation for complex geometries. positioned in the market?
Based on our AI analysis of the original developer request, its primary technical positioning is: Accurate geometric representation and conversion for CAD/BRep data within the USD ecosystem. The goal is precise area calculation, which is failing to converge with increased accuracy settings.
What architecture is tied to usd-brep library, specifically occt_to_usd conversion for NURBS-based boundary representation (BRep) solid modeling, with a focus on accurate area calculation for complex geometries.?
Our proprietary extraction maps usd-brep library, specifically occt_to_usd conversion for NURBS-based boundary representation (BRep) solid modeling, with a focus on accurate area calculation for complex geometries. to adjacent architectural concepts including USD BRep, NURBS-based boundary representation (BRep) solid modeling, occt_to_usd, planar face.

Engagement Signals

0
Replies
open
Issue Status

Cross-Market Term Frequency

Quantifies the cross-market adoption of foundational terms like trim and USD BRep by tracking occurrence frequency across active SaaS architectures and enterprise developer debates.