geometry op• Data kinds: none → table (an op determined by its arguments alone — it takes no image or data input)
• Call: import fullseye as fs; fs.ledger.nurbs_circle(radius: 'float' = 1.0, center=(0.0, 0.0)) -> 'dict' (to call the implementation directly, import mathgeometry; mathgeometry.nurbs_circle(radius: 'float' = 1.0, center=(0.0, 0.0)) -> 'dict'; from the registry, opsmath.get("nurbs_circle"))
> This operator's description has not been translated yet. The original text follows as it is.
円を厳密に表す 2 次 NURBS(Piegl & Tiller 例 7.1: 正方形の 4 隅と 4 辺の中点、隅の重みは 1/√2)。
返す `control_points・weights・knots・degree をそのまま nurbs_curve` に渡すと、どの点も中心から
`radius` の距離にある(丸め誤差まで)。隅の制御点は円の外 (√2 − 1)·radius の所にあり、曲線は通らない。
Every mathops op validates its input before computing (nothing slips through silently):
• **complex input raises ValueError** — coercing to float64 silently discards the imaginary part (numpy only emits a ComplexWarning and returns a plausible-looking wrong real number). State .real/.imag/abs() explicitly, or use complexops, which handles complex data.
• **masked arrays with masked elements raise ValueError** — the implicit conversion that peels off the mask and uses the raw values underneath is refused. Say explicitly whether to fill or to drop.
• **NaN/Inf raises ValueError on every input** (refused with the count stated — it propagates through the whole result).
• Shapes are strict: 1-D and 2-D are never implicitly promoted or broadcast (a matrix in a vector slot, or a vector in a matrix slot, raises ValueError; reshape explicitly).
• Size cap: ops that take a matrix, and the stat_histogram bins, raise ValueError beyond mathops.MAX_ELEMENTS (2^26 ≈ 67 million elements).
• Sample-data catalog (download URLs / licences) — 2-D uses skimage.data (BSD/public domain) plus synthetic images; 3-D lists download URLs for real data sources (Stanford, PDS, …).
• Operator provenance and references — the sources of the research/methods this op family came from.
• The canonical algorithm (author, year) and its uses are named in the family usage guide above.
• geometry_tour — py -3.11 examples/geometry_tour.py
table as input)dynsys_poincare_section · dwt_inverse · chebyshev_eval_nd
geometry)mesh_euler_characteristic · angle_defect · delaunay_triangulate · geodesic_heat · geodesic_heat_grid · mesh_torus · nurbs_curve · nurbs_surface
*Provenance: mathgeometry.py — MATH operator registry. This per-op note is generated by tools/opdocs.py md (do not hand-edit).*
© 2026 Kazufumi Furuse — Fullseye operator documentation. Licensed under Apache-2.0.