Skip to content

Main content

Edit Gap Extension Term Tool

Evaluate one affine gap cost using opening+(length−1)*extension and zero cost for an empty gap.

Loading tool…

Description

Evaluate one affine gap cost using opening+(length−1)*extension and zero cost for an empty gap.

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.

Evaluate one affine gap cost using opening+(length−1)*extension and zero cost for an empty gap.

When to use this tool

Use Edit Gap Extension Term 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 gapLength, openingCost, extensionCost. 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 cost. Use the output convention below.

Return zero for gapLength zero, otherwise openingCost+(gapLength-1)*extensionCost. Require nonnegative integer length and nonnegative costs.1

Input fieldMeaning and unitsAccepted input
gapLengthGap LengthRequired. Safe integer; minimum 0.
openingCostOpening CostRequired. Finite number; minimum 0.
extensionCostExtension CostRequired. Finite number; minimum 0.
Output fieldInterpretationReturned shape
costCostRequired. Finite number.
json
{
  "input": {
    "gapLength": 4,
    "openingCost": 5,
    "extensionCost": 2
  },
  "output": {
    "cost": 11
  }
}

Limitations and assumptions

  • The first gap item incurs opening cost only under this affine-gap convention. No alignment, gap placement, scoring optimization, or alternative opening-plus-full-length convention is inferred.
  • 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/edit-gap-extension-term — tool.io

Similar or alternative tools