Skip to content

Main content

List Adjacent Delta Missing Policy Tool

Compute list adjacent delta missing policy from explicit bounded inputs.

Loading tool…

Description

For each adjacent pair return next minus previous when both are present; otherwise return delta zero and valid false.

An adjacent delta requires two available values. A missing endpoint should be carried as an unavailable result rather than silently interpreted as a measured zero change.

For each adjacent pair return next minus previous when both are present; otherwise return delta zero and valid false.

When to use this tool

Use List Adjacent Delta Missing Policy when you need adjacent differences with aligned missing-value flags.

How to use the tool and how it works

  1. Enter values, missing. Keep parallel arrays aligned. Use the units and conventions below.
  2. Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
  3. Read deltas, valid. Use the output convention below.

Require aligned values and missing flags. For each adjacent pair return next minus previous when both are present; otherwise return delta zero and valid false.1

Input fieldMeaning and unitsAccepted input
valuesValuesRequired. Array of finite number; maximum items 256.
missingMissingRequired. Array of boolean; maximum items 256.
Output fieldInterpretationReturned shape
deltasDeltasRequired. Array of finite number; maximum items 256.
validWhether this narrowly scoped condition passes; it is not necessarily full-document validity.Required. Array of boolean; maximum items 256.
json
{
  "input": {
    "values": [
      2,
      5,
      9
    ],
    "missing": [
      false,
      false,
      true
    ]
  },
  "output": {
    "deltas": [
      3,
      0
    ],
    "valid": [
      true,
      false
    ]
  }
}

Limitations and assumptions

  • Invalid zeros are placeholders and must be read with valid; gaps are not bridged or imputed.
  • Inputs must satisfy both the field types and the cross-field conditions above. Invalid input causes an error; a successful false flag or documented placeholder is a different result.
  • Numeric calculations use binary floating point unless exact decimal-integer arithmetic is explicitly stated. No hidden measurement tolerance or decimal rounding is added; nonfinite or out-of-contract results are rejected. Numeric signed-zero results are exported as zero.

Alternative or Complementary methods

Retain missingness through aggregation and choose a separate interpolation or gap-bridging policy if needed.

References

  1. Calculation and input contract: list/list-adjacent-delta-missing-policy — tool.io

Similar or alternative tools