Microburst vs Macroburst Classifier

Observed downburst footprint/duration/wind evidence against caller micro/macroburst classification, not storm safety. Independently declared positive evidence requirements; overlapping/unknown classes retained. Caller independently establishes matching units, evidence, method edition and applicability; output is not compliance, diagnosis, work-safety approval, geological identity or validated hazard prediction.

Description

Microburst and macroburst labels concern the spatial extent of a downburst.

Microburst and macroburst labels concern the spatial extent of a downburst.^[1]

Establish the footprint and the adopted classification criteria before comparing evidence. The tool compares your observed and known flags with your declared positive requirements, retaining unresolved candidates.

When to use Microburst vs Macroburst Classifier

Use this tool to calculate or review the supplied observations under the stated rules. Establish the observation method, units, averaging period and applicable reference or calibration.

How to use Microburst vs Macroburst Classifier and understand its results

Establish the observation method, units, averaging period and applicable reference or calibration.
Enter callerDownburstFootprintClassIds, callerDownburstFootprintRequiredEvidence, observedDownburstFootprintEvidence, knownDownburstFootprintEvidenceFlags, using the field meanings and rules below, then run the tool.
Read compatibleCallerClasses, fullyWitnessedCallerClasses, using the output meanings and calculation rules below. Distinguish compatible candidates from fully witnessed classes; compatibility can retain unknown required evidence.
Correct any reported input issue and run again. Before using a successful result, check the stated units, signs, reference scope and observation coverage.

Input field	Meaning	Value type	Requirement
callerDownburstFootprintClassIds	Caller downburst footprint class ids	list of string	Required
callerDownburstFootprintRequiredEvidence	Caller downburst footprint required evidence	numeric matrix	Required
observedDownburstFootprintEvidence	Observed downburst footprint evidence	list of number	Required
knownDownburstFootprintEvidenceFlags	Known downburst footprint evidence flags; binary 1 means the matched observation is known, 0 means unknown	list of number	Required

Use unique nonblank class IDs and a nonempty binary requirement matrix aligned by class and evidence column. Every class must require at least one positive feature. A one requires presence; zero ignores the feature and does not require absence. Supply binary observed evidence and known flags. A known required zero excludes a class; an unknown required feature retains compatibility but prevents full witnessing. Return all compatible classes and the subset with every required feature known and present. Classes may overlap.

compatible_c=∀j(requirement_cj=0 or known_j=0 or evidence_j=1); witnessed_c=∀j(requirement_cj=0 or (known_j=1 and evidence_j=1))

Use the matching field units and the exact boundary, ordering and reference rules above.

Output field	Meaning	Value type
compatibleCallerClasses	Compatible caller classes	list of string
fullyWitnessedCallerClasses	Fully witnessed caller classes	list of string

json

{
  "input": {
    "callerDownburstFootprintClassIds": [
      "a",
      "b"
    ],
    "callerDownburstFootprintRequiredEvidence": [
      [
        1,
        0
      ],
      [
        0,
        1
      ]
    ],
    "observedDownburstFootprintEvidence": [
      1,
      0
    ],
    "knownDownburstFootprintEvidenceFlags": [
      1,
      0
    ]
  },
  "output": {
    "compatibleCallerClasses": [
      "a",
      "b"
    ],
    "fullyWitnessedCallerClasses": [
      "a"
    ]
  }
}

Limitations and assumptions

The observations and reference conditions must be independently established. This result does not supply missing measurements, uncertainty or an official warning. Compatible classes with unknown evidence are not positive identifications. Fully witnessed classes satisfy only the declared positive requirements.

Missing required fields, unknown fields, wrong types and violated rules return input issues. Numeric values and outputs must be finite. Lists and matrices must be dense, without missing cells. Numeric lists allow at most 10000 entries; ordinary string lists allow at most 128 strings of 128 UTF-16 units each; numeric matrices allow at most 128 rows and 128 columns, subject to narrower requirements above.

Alternative or Complementary methods

For a related step, use Low Level Wind Shear Alert Threshold Checker: An along-runway wind change has a sign, while a magnitude threshold screens changes in either direction. For a complementary comparison, use DCAPE Downdraft CAPE Calculator: Downdraft CAPE represents integrated favorable downdraft buoyancy along an independently supplied parcel profile.

References

Microburst vs Macroburst Classifier — tool.io

Similar or alternative tools

Low Level Wind Shear Alert Threshold Checker
An along-runway wind change has a sign, while a magnitude threshold screens changes in either direction.
DCAPE Downdraft CAPE Calculator
Downdraft CAPE represents integrated favorable downdraft buoyancy along an independently supplied parcel profile.