Kerf.Kernel.ModelingData 0.4.0

There is a newer version of this package available.
See the version list below for details.
dotnet add package Kerf.Kernel.ModelingData --version 0.4.0
                    
NuGet\Install-Package Kerf.Kernel.ModelingData -Version 0.4.0
                    
This command is intended to be used within the Package Manager Console in Visual Studio, as it uses the NuGet module's version of Install-Package.
<PackageReference Include="Kerf.Kernel.ModelingData" Version="0.4.0" />
                    
For projects that support PackageReference, copy this XML node into the project file to reference the package.
<PackageVersion Include="Kerf.Kernel.ModelingData" Version="0.4.0" />
                    
Directory.Packages.props
<PackageReference Include="Kerf.Kernel.ModelingData" />
                    
Project file
For projects that support Central Package Management (CPM), copy this XML node into the solution Directory.Packages.props file to version the package.
paket add Kerf.Kernel.ModelingData --version 0.4.0
                    
#r "nuget: Kerf.Kernel.ModelingData, 0.4.0"
                    
#r directive can be used in F# Interactive and Polyglot Notebooks. Copy this into the interactive tool or source code of the script to reference the package.
#:package Kerf.Kernel.ModelingData@0.4.0
                    
#:package directive can be used in C# file-based apps starting in .NET 10 preview 4. Copy this into a .cs file before any lines of code to reference the package.
#addin nuget:?package=Kerf.Kernel.ModelingData&version=0.4.0
                    
Install as a Cake Addin
#tool nuget:?package=Kerf.Kernel.ModelingData&version=0.4.0
                    
Install as a Cake Tool

Kerf.Kernel

A managed .NET CAD kernel derived from Open CASCADE Technology (OCCT) 8.0.1, ported to C# and redesigned for .NET. See docs/api for the public API, docs/design.md for the design and docs/port-status.md for what has been ported.

  • Pure managed code: no native libraries, no P/Invoke.
  • .NET names: the public API is in namespaces by area (Kerf.Geometry, Kerf.Topology, Kerf.Booleans…), without OCCT's package prefixes, and members follow .NET's naming. The algorithms are internal, in Kerf.Engine.<Area>. docs/api/kerf.map says what each OCCT name became, so OCCT's documentation can still be found; each derived file names its OCCT source in a // Port of: header.
  • Immutable: every value you get back is immutable.
  • Results: an operation that can fail for an expected reason returns a Result, with diagnostics.
using Kerf.Geometry;

Transform3D rotation = Transform3D.Rotation(Axis3D.ZAxis, Math.PI / 2);
Point3D point = new Point3D(1, 0, 0).Transformed(rotation);   // (0, 1, 0); the original is unchanged

Assemblies

Assembly What
Kerf.Kernel.Foundation Maths, geometric values (Point3D, Transform3D…), bounding boxes, the engine's foundations
Kerf.Kernel.ModelingData Curves and surfaces, topology (Shape, Edge, Face…), adaptors, extrema
Kerf.Kernel.ModelingAlgorithms Construction, Booleans, fillets, offsets, features, healing, meshing
Kerf.Kernel.DataExchange STEP, STL, glTF, 3MF, OBJ and BREP

Runtime settings for a host

These belong to the application, not the library. For work on many threads, such as a spreadsheet recalculating workbooks at once:

<PropertyGroup>
  <ServerGarbageCollection>true</ServerGarbageCollection>
  <ConcurrentGarbageCollection>true</ConcurrentGarbageCollection>
  <TieredPGO>false</TieredPGO>
</PropertyGroup>
<ItemGroup>
  <RuntimeHostConfigurationOption Include="System.Runtime.TieredCompilation.CallCountingDelayMs" Value="0" />
</ItemGroup>

Measured on 24 logical processors, a round of 24 copies of Bento's examples takes 620 ms against 2,700 ms with the runtime's defaults, and a single recalculation 180 ms against 360, at a peak of about 400 MB against 200. Leave the server collector's dynamic adaptation (DATAS) on: turning it off gains little and takes about 700 MB. Without PGO, code that has settled for minutes is about 6% slower, so a long batch job may prefer to leave it on. See docs/performance.md, "Unit 11D".

No tiering setting beyond these helps opening (unit 11C tried quick JIT, quick JIT for loops, on-stack replacement and the background worker's timeout). An application that ships its own runtime can go further by publishing self-contained with PublishReadyToRunComposite: opening 419 ms against 509 on Bento's examples, at 169 MB for the whole application, measured on assemblies built from source rather than from the packages. If it publishes ReadyToRun at all, setting PublishReadyToRunCrossgen2ExtraArgs to --opt-cross-module:*;--Ot, as Kerf's packages do, should help its own generics over Kerf's types (not measured).

Building

Requirements: the .NET 10 SDK and git.

./tools/get-occt.ps1          # OCCT V8_0_1 source into .deps/occt-src (for the corpus test and port status)
./tools/get-occt-testdata.ps1 # OCCT's test data (99 MB) into .deps/occt-testdata, for the Draw corpus
dotnet test

tests/Kerf.Kernel.Oracle.Tests compares the port with native OCCT's results, recorded when native OCCT was still built (unit 10A) and frozen since it went (unit 10B): see docs/oracle-testing.md.

Contributing

docs/design-rules.md gives the rules for new and redesigned code (phase 10); docs/translation-rules.md says how C++ became C# until phase 10, and docs/porting-playbook.md the steps for porting a package.

Licence

GNU Lesser General Public License 2.1 with the Open CASCADE exception, as OCCT: see LICENSE, OCCT_LGPL_EXCEPTION.txt and NOTICE. Kerf.Kernel is a modified version of OCCT 8.0.1 and isn't endorsed by Open Cascade SAS. Delabella's port (BRepMesh/delabella.cs) keeps its MIT licence: see THIRD-PARTY-NOTICES.md.

Product Compatible and additional computed target framework versions.
.NET net10.0 is compatible.  net10.0-android was computed.  net10.0-browser was computed.  net10.0-ios was computed.  net10.0-maccatalyst was computed.  net10.0-macos was computed.  net10.0-tvos was computed.  net10.0-windows was computed. 
Compatible target framework(s)
Included target framework(s) (in package)
Learn more about Target Frameworks and .NET Standard.

NuGet packages (1)

Showing the top 1 NuGet packages that depend on Kerf.Kernel.ModelingData:

Package Downloads
Kerf.Kernel.ModelingAlgorithms

Kerf.Kernel modelling algorithms, derived from Open CASCADE Technology 8.0.1 (Open Cascade SAS), ported to C# and redesigned: a port of OCCT's TKGeomAlgo, TKTopAlgo and TKPrim (intersections, classification, topological algorithms, primitives).

GitHub repositories

This package is not used by any popular GitHub repositories.

Version Downloads Last Updated
0.5.0 70 11/10/2026
0.4.0 113 11/9/2026
0.3.0 108 11/8/2026
0.2.0-preview.2 81 11/4/2026