Skip to content

Main content

Ochiai Binary Count Normalizer Tool

Calculate ochiai binary count normalizer from explicit caller-supplied inputs.

Loading tool…

Description

Return normalizer=sqrt(firstSize*secondSize) and score=intersection/normalizer.

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.

Return normalizer=sqrt(firstSize*secondSize) and score=intersection/normalizer.

When to use this tool

Use Ochiai Binary Count Normalizer 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 intersection, firstSize, secondSize. 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 normalizer, score. Use the output convention below.

Return normalizer=sqrt(firstSize*secondSize) and score=intersection/normalizer. Require positive integer sizes and feasible intersection count.1

Input fieldMeaning and unitsAccepted input
intersectionIntersectionRequired. Safe integer; minimum 0.
firstSizeFirst SizeRequired. Safe integer; minimum 1.
secondSizeSecond SizeRequired. Safe integer; minimum 1.
Output fieldInterpretationReturned shape
normalizerNormalizerRequired. Finite number.
scoreScoreRequired. Finite number.
json
{
  "input": {
    "intersection": 3,
    "firstSize": 4,
    "secondSize": 9
  },
  "output": {
    "normalizer": 6,
    "score": 0.5
  }
}

Limitations and assumptions

  • This is the binary-count Ochiai normalizer, not a general real-vector cosine. Actual set membership, feature weighting, and empty-support conventions are not 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/ochiai-binary-count-normalizer — tool.io

Similar or alternative tools