Skip to content

Risk H2: make the deployable pipeline genuinely headless (Rhino-free Core paths) #14

Description

@libishm1

From the risk register (H2): 78 of 300 Core files import RhinoCommon (geology/discontinuity, fabrication DXF/cut-plan/wire-saw, much of masonry). A 'headless server' would need Rhino.Compute for those, not a plain dotnet service. The 2D nester (ContactNfpHoleNester) and its Core packing path are already clean.

Task: for each Core path intended for headless/service use, replace RhinoCommon geometry types (Point3d/Vector3d/Transform/Mesh/BoundingBox) with the Rhino-free Core primitives (Vec3/MeshTriangle/Box3) that already exist. Prioritize by service value: (1) 2D nesting = already clean (reference); (2) block-cut/DXF export; (3) geology feasibility. TreePackForest.cs and RubbleWallSettle.cs are the known Rhino-bound blockers.

Done when: grep -rl 'using Rhino' src/Frahan.StonePack.Core covers only genuinely Rhino-coupled paths, and the target service paths compile+test in a project that does not reference RhinoCommon. Size: L (incremental per path). Prereq for any headless Compute/CLI deployment.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    blueprintA self-contained node of the collaboration blueprint (see CONTRIBUTING.md)

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions