Description
For positive component and geometricMean return value=ln(component/geometricMean).
Normalization depends on the supplied center, scale, norm, range, reference distribution, or denominator. A zero spread and a missing denominator need an explicit policy, and clipping differs from fitting a scaler. Evaluating one scalar or derivative term does not estimate every parameter or establish a distributional improvement.
For positive component and geometricMean return value=ln(component/geometricMean).
When to use this tool
Use CLR Logratio One Component Value when you already have the required normalization parameters and need this local scalar, range, policy, or derivative term.
How to use the tool and how it works
- Enter component, geometricMean. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read value. Use the output convention below.
For positive component and geometricMean return value=ln(component/geometricMean).1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| component | Component | Required. Finite number; strictly above 0. |
| geometricMean | Positive supplied compositional geometric mean on the component unit basis. | Required. Finite number; strictly above 0. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| value | Supplied scalar or returned value under the stated operation. | Required. Finite number. |
{
"input": {
"component": 4,
"geometricMean": 2
},
"output": {
"value": 0.6931471805599453
}
} Limitations and assumptions
- Both inputs need one unit and the geometric mean must already represent the intended positive composition. The tool does not compute that mean or all centered-logratio coordinates; direct division can overflow or underflow even when separate logarithms would be finite.
- 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
Fit or verify the intended scaler parameters and statistical model separately. Check units, zero policies, missingness, clipping, inverse conventions, and whether supplied norms or denominators belong to the same data.
References
Similar or alternative tools
- Normalization: Signed Log1p Reference Scale
Apply an odd signed-log1p transform with an explicitly supplied positive reference scale, preserving zero without imposing an undefined logarithm on negatives.
- Boxcox Lambda Zero Continuity Bridge
For positive value return zeroLimit=ln(value) and transformed=zeroLimit when lambda==0, otherwise expm1(lambda*ln(value))/lambda.