AlphaShapes

org.appliedtopology.tda4j.alpha.AlphaShapes
See theAlphaShapes companion class
object AlphaShapes

apply/Point are scoped here rather than as bare top-level alpha package defs (a generic name like Point, or a dispatch function as central as Alpha used to be, is exactly the kind of top-level-name collision hazard documented elsewhere in this codebase) -- callers write AlphaShapes(points, dispatch). import AlphaShapes.Point below brings both the type and its factory back into unqualified scope for the rest of this file, where Point is used pervasively by Hyperplane/Hypersphere/HelixDelaunay.

Attributes

Companion
class
Experimental
true
Graph
Supertypes
class Object
trait Matchable
class Any
Self type

Members list

Type members

Classlikes

object Point

Attributes

Supertypes
class Object
trait Matchable
class Any
Self type
Point.type

Types

type Point = RealVector

Value members

Concrete methods

def apply(pts: Seq[Array[Double]], dispatch: String = ..., requireValidTriangulation: Boolean = ...)(using epsilon: Epsilon = ...): AlphaShapes

Value parameters

requireValidTriangulation

OFF by default. Only meaningful for the "helix"/"default" backend -- threaded straight through to HelixDelaunay's own constructor parameter of the same name (.claude/DESIGN-helix-triangulation-repair.md). required false for dispatch="dqp": AlphaShapeDQP has no facet-multiplicity precondition to repair in the first place (it is not FastAlphaHomologyContext's own backend), so a caller passing true there almost certainly mis-set the option rather than intending a silent no-op.

Attributes