Description
Check whether a supplied affine normalization collides with a missing sentinel.
Normalization requires an explicit order of operations, center, scale and reference convention. Centering before scaling generally differs from subtracting the same center after scaling. A normalized weight or bounded uncertainty interval inherits supplied assumptions; zero entries, sentinel collisions and reference-category coding need separate interpretation.
Check whether a supplied affine normalization collides with a missing sentinel.
When to use this tool
Use Scaled Missing Sentinel Collision Check when you already have observedValue, center, scale, missingSentinel and need to check whether a supplied affine normalization collides with a missing sentinel.
How to use the tool and how it works
- Enter observedValue, center, scale, missingSentinel. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read scaledValue, collidesWithSentinel. Inspect collidesWithSentinel before interpreting the associated values.
Compute (observedValue-center)*scale and compare the result to missingSentinel by exact numeric equality.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| observedValue | Observed Value | Required. Finite number. |
| center | Center | Required. Finite number. |
| scale | Scale | Required. Finite number. |
| missingSentinel | Missing Sentinel | Required. Finite number. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| scaledValue | Scaled Value | Required. Finite number. |
| collidesWithSentinel | Exact equality of scaledValue and missingSentinel; no tolerance or missing-data imputation. | Required. Boolean. |
{
"input": {
"observedValue": 5,
"center": 1,
"scale": 2,
"missingSentinel": 8
},
"output": {
"scaledValue": 8,
"collidesWithSentinel": true
}
}Limitations and assumptions
- No tolerance, missing-value policy or data distribution is inferred; zero scale and signed values are allowed.
- 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
Specify the intended transformation and data basis before estimating or applying parameters. Review missing-value handling and reference coding across the full dataset; one affine term or normalized vector does not establish comparable measurements or a fitted model.
References
Similar or alternative tools
- Scalar Centering After Scaling Delta
Compare centering before scaling with centering after scaling.
- Robust Center Uncertainty Shift
Propagate a supplied center-uncertainty bound through positive-scale normalization.