Point Probe

Reads analysis values at any points (entrances, seating, play areas...). Interpolates within the mesh face, works for several result sets at once (options, hours) and writes a CSV table for reports.

Site Analysis Nickname: Probe

Overview

Reads analysis values at any points (entrances, seating, play areas...). Interpolates within the mesh face, works for several result sets at once (options, hours) and writes a CSV table for reports.

Inputs (8)

  • Mesh (Mesh): Analysis mesh
  • Values (Number): One value per vertex or per face. Several branches = several result sets (options, hours); each becomes a CSV column
  • Points (Point): Points to probe
  • Names (Text): Optional name per point (default P1, P2...)
  • SetNames (Text): Optional name per result set / branch (default from branch path)
  • MaxDistance (Number): Points further than this from the mesh get no value (0 = no limit)
  • Decimals (Integer): Decimals in labels and CSV
  • Unit (Text): Unit shown in the labels, e.g. m/s, dB, h

Outputs (5)

  • Values (Number): Probed value per point (one branch per result set, same order as Points). Empty where the point is off the mesh
  • MeshPoints (Point): Closest point on the mesh for each probe (label anchors)
  • Labels (Text): Name: value text per point (first result set; all sets when there are several)
  • CSV (Text): Table Name,X,Y,Z,<set 1>,<set 2>... (paste into Excel or write with a file writer)
  • Info (Text): Component information and interpretation

Method, assumptions and simplifications

The same notes appear in the component's Info output.

Method

  1. Each probe point is moved to the closest point on the Mesh (ignored if further than MaxDistance; 0 = no limit).
  2. For per-vertex values the result is interpolated with the barycentric weights of that point inside the hit face; vertices with no value are left out and the weights rescaled. For per-face values the face value is used. If the mesh has as many vertices as faces, values are read as per-vertex and a warning flags the ambiguity.
  3. Each branch of Values is one result set and one CSV column; branches must have one value per vertex or per face.
  4. Labels show name: value(s) unit; the CSV has Name, X, Y, Z (closest mesh point, 2 decimals) and one column per set.

Assumptions

  • Values are in the same order as the mesh vertices or faces they came from.

Simplifications and limits

  • No search for the best face when several are equally close; values are only as fine as the mesh.

Workflow

  • Any analysis mesh and its values (Sun Hours, Fast Noise, wind) -> Mesh and Values; Labels and MeshPoints -> Text Tag 3D.