Skip to content

Main content

Normalized Edit Similarity Endpoint Check Tool

Compute normalized edit similarity endpoint check from explicit bounded inputs.

Loading tool…

Description

Check nonnegative integer distance against the length-based bounds abs(leftLength-rightLength)<=distance<=max(lengths), then return one-distance/max(lengths), using one for both-empty inputs.

A similarity term depends on the comparison universe, missing-value policy, treatment of repeated features, and normalization. A score can also have a caller-selected value when its mathematical denominator vanishes. Those conventions matter before interpreting a threshold or comparing methods.

Check nonnegative integer distance against the length-based bounds abs(leftLength-rightLength)<=distance<=max(lengths), then return one-distance/max(lengths), using one for both-empty inputs.

When to use this tool

Use Normalized Edit Similarity Endpoint Check when you need this particular comparison term, normalization, domain condition, or empty-result policy in a larger matching workflow.

How to use the tool and how it works

  1. Enter distance, leftLength, rightLength. 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 valid, similarity. Inspect valid before interpreting the associated values.

Check nonnegative integer distance against the length-based bounds abs(leftLength-rightLength)<=distance<=max(lengths), then return one-distance/max(lengths), using one for both-empty inputs.1

Input fieldMeaning and unitsAccepted input
distanceDistanceRequired. Safe integer; minimum 0.
leftLengthLeft LengthRequired. Safe integer; minimum 0.
rightLengthRight LengthRequired. Safe integer; minimum 0.
Output fieldInterpretationReturned shape
validWhether this tool’s specific rule passes, not a broader approval.Required. Boolean.
similaritySimilarityRequired. Finite number.
json
{
  "input": {
    "distance": 0,
    "leftLength": 0,
    "rightLength": 0
  },
  "output": {
    "valid": true,
    "similarity": 1
  }
}

Limitations and assumptions

  • The bounds assume unit-cost edit operations and failures are input errors. Passing them does not prove an actual edit distance or matching strings; no edits are computed.
  • The field tables state structural bounds; the mechanics also specify cross-field constraints. Malformed inputs and unsupported domains cause errors. A successful false flag, empty branch value, or zero placeholder has the meaning stated above and is distinct from an input error.
  • 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. Signed zero is exported as zero.

Alternative or Complementary methods

Compare methods only after aligning feature definitions, missingness, empty policies, multiplicities, and normalizers. Use a complete comparison when the tool returns only one contribution or count check.

References

  1. Calculation and input contract: similarity/normalized-edit-similarity-endpoint-check — tool.io

Similar or alternative tools