▼V Reference
52 Find a task or a name
53 Modules to require
54 Scenes and sampling
55 Scene states
56 Animation requests
57 Native model details
58 Visuals
59 Geometry
60 Number Lines and Coordinate Decorations
61 Point Markers, Scatter Plots, and Filled Areas
62 Probability and Statistical Diagrams
63 Calculus lessons
64 Colors
65 Slides
66 Slide command-line tools
67 Source Programs and Authored Timelines
68 Interactive Preview and Inspection
69 Preview controls and diagnostics
70 Projects and Final Rendering
71 Project execution and cache details
72 Pict Renderer Protocol
73 3D reference map
74 3D:   Objects, groups, and paths
75 3D:   Cameras and projection
76 3D:   Views inside a Scene
77 3D:   Animating 3D objects
78 3D:   Animating the 3D camera
79 3D:   Cuts, caps, and section measurements
80 3D:   Supplementary surface, section, and annotation bindings
81 3D:   Cuts, sections, and numerical volume
82 3D:   Vectors
83 3D:   Linear maps and rotations
84 3D:   Affine transforms
85 3D:   Bounds, rays, and planes
86 3D:   Spatial maps and homotopies
87 3D:   Materials and lights
88 3D:   Lighting inspection
89 3D:   Shadow descriptors and stable bounds
90 3D:   Finite-light animation
91 3D:   Software finite-light evaluation
92 3D:   Colour space and final output
93 3D:   Relations and geometric annotations
94 3D:   Projected labels
95 3D:   Textured billboards
96 3D:   Spatial curves and vector diagrams
97 3D:   Spatial anchors and label layout
98 3D:   Anchors and projected labels
99 3D:   Parametric surfaces and calculus
100 3D:   Adaptive, trimmed, and implicit surfaces
101 3D:   Constructive solids
102 3D:   Surface constructors and queries
103 3D:   Meshes
104 3D:   Triangle topology
105 3D:   Polygonal faces
106 3D:   Deterministic convex hulls
107 3D:   Polyhedral duals
108 3D:   Schlegel diagrams and polyhedral nets
109 3D:   Conservative mesh correspondence
110 3D:   Topology-safe mesh matching
111 3D:   Checking and repairing mesh orientation
112 3D:   Clipping, sections, and transparency
113 3D:   Prepared spatial ODE trajectories and vector fields
114 3D:   Seeds and streamline sets
115 3D:   Poincare sections and return maps
116 3D:   Equilibria and local linearization
117 3D:   Flow maps and volume change
118 3D:   Drawing and inspecting trajectories
119 3D:   Reading prepared trajectories
120 3D:   Drawing vector fields and particles
121 3D:   Trajectory display
122 3D:   Spatial inspection and exact picking
123 3D:   Retained renderer backends
124 3D:   Compiled geometry and instances
125 3D:   Frame requests and results
126 3D:   Software rendering and statistics
127 3D:   Optional Racket/  Open  GL backend
128 Experimental Derived Visuals
129 Source Package Hygiene
On this page:
poincare-section3d
poincare-hit3d?
poincare-hit3d-plane-coordinates
poincare-hits3d
prepare-poincare-map3d
prepared-poincare-map3d?
9.3

115 3D: Poincare sections and return maps🔗ℹ

procedure

(poincare-section3d trajectory 
  plane 
  [#:trajectory-id trajectory-id 
  #:direction direction 
  #:tolerance tolerance 
  #:deduplicate-time deduplicate-time 
  #:tangent-policy tangent-policy 
  #:initial-hit initial-hit]) 
 → vector?
  trajectory : prepared-trajectory3d?
  plane : plane3?
  trajectory-id : symbol? = 'trajectory
  direction : (or/c 'any 'positive 'negative) = 'any
  tolerance : positive? = 1e-8
  deduplicate-time : positive? = tolerance
  tangent-policy : (or/c 'ignore 'include) = 'ignore
  initial-hit : (or/c 'include 'exclude 'require) = 'exclude
Extracts immutable poincare-hit3d? crossings by running the event root finder over retained dense trajectory segments. A positive/negative direction means increasing/decreasing signed distance along increasing physical time. Shared endpoint roots are time-deduplicated; a tangent contact is omitted unless explicitly included. The default 'exclude omits a qualifying hit at the trajectory’s range start so a return map begins with its first return. 'include retains it, and 'require retains it but reports an error when the trajectory does not start on the section.

procedure

(poincare-hit3d? value) → boolean?

  value : any/c
Recognizes an immutable crossing record. Its accessors begin with poincare-hit3d-; source-event is the serializable dense root record, not an event procedure.

procedure

(poincare-hit3d-plane-coordinates hit    
  plane) → vector?
  hit : poincare-hit3d?
  plane : plane3?
Returns the point’s deterministic two-coordinate plane basis projection, suitable for an ordinary two-dimensional plot.

procedure

(poincare-hits3d hits #:id id #:style style) → group3d?

  hits : (or/c list? vector?)
  id : symbol?
  style : any/c
Lowers hit values to ordinary spatial point markers.

procedure

(prepare-poincare-map3d 
  field 
  plane 
  seeds 
  [#:direction direction 
  #:tangent-policy tangent-policy 
  #:initial-hit initial-hit 
  #:parallel? parallel? 
  #:cancellation-token cancellation-token]) 
 → prepared-poincare-map3d?
  field : any/c
  plane : plane3?
  seeds : seed-set3d?
  direction : (or/c 'any 'positive 'negative) = 'any
  tangent-policy : (or/c 'ignore 'include) = 'ignore
  initial-hit : (or/c 'include 'exclude 'require) = 'exclude
  parallel? : (or/c boolean? 'auto) = 'auto
  cancellation-token : any/c = #f
Prepares per-seed first and second crossings. Missing returns remain #f in the same seed slot; the result is not a claim that an arbitrary flow has a global return map. Independent trajectory preparation may use bounded worker threads but retains seed order.

procedure

(prepared-poincare-map3d? value) → boolean?

  value : any/c
Recognizes an immutable per-seed return-map record. Its accessors begin with prepared-poincare-map3d-.