AMVero classifies anomalies as Critical or Moderate, but each detection is evaluated on a single layer in isolation. This means a small anomaly can trigger a Critical alert on one layer but never grow further, yet the operator still gets notified. With no way to factor in how an anomaly behaves over multiple layers, operators receive alerts that don't reflect actual build risk.
Add a second filtering layer on top of Critical/Moderate classification. Users define conditions based on aggregated, multi-layer anomaly data — volume, growth rate, spatial properties — so an alert fires only when the combined conditions justify it.
Smart Alerting gives users the ability to define alerts based on the measurable
characteristics of an aggregated anomaly, not just its type and severity. Users define
quantitative trigger conditions (e.g. volume > 5mm³,
growth_rate > 20%) that must be satisfied before an alert fires, replacing the
binary logic of earlier versions where any matching anomaly would trigger a notification.
Warpage · Recoater Line · Recoater Hopping · Short Feed (Critical + Moderate)
| Property | Description | LPBF Use Case |
|---|---|---|
| anomaly_height (absolute) |
Total Z extent (mm) | Alert if defect spans >X mm |
| anomaly_height (layers) |
Z extent in layer count | Alert if spanning >X layers |
| volume | 3D volume (mm³) | Alert if total defect volume >X mm³ |
| growth_rate | Percentage acceleration in volumetric growth. Compares growth between last 2 intervals. Min 3 layers. | Alert if growing faster than X voxels/layer |
| 2d_area | Area on current layer (mm²) | Alert if current layer anomaly >X mm² |
| surface_area | 3D surface area of aggregated anomaly (mm²) | Alert if surface is irregular >X mm² |
| volume / surface_area | Compactness metric | Alert if defect is dense vs spread out |
| volume / height | Shape metric | Alert if defect is flat vs tall |
| current_2d_area / build_plate | % of build plate affected | Alert if anomaly covers >X% of build area |
| distance_from_edge (recoater) |
mm from edge, recoater direction | Alert if anomaly is near powder bed edge |
| distance_from_edge (orthogonal) |
mm from edge, perpendicular to recoater | Alert if anomaly is near powder bed edge |
| intersect_with | Binary intersection with Part, or [Anomaly Type + Severity] | Alert if anomaly intersects specific target |
Note: intersect_with is binary only — no operator or value required.
Controls how many times an alert can fire for a single aggregated anomaly.
The alert fires once, the first time the trigger conditions are satisfied for a given aggregated anomaly. Preserves the existing alerting policy.
Re-evaluates on each new layer and fires again every time conditions are met for the same anomaly. Intended for properties that fluctuate layer to layer, such as Growth Rate or current layer 2D Area.