From an Additive Score to a Probability
A boosted classifier may build its prediction by adding the contributions of successive learners. When the model uses the logistic convention, this running score is not itself a probability: it represents the log odds of the positive class. Converting that score correctly matters because a score change has a simple effect on odds, but its effect on probability depends on the current score.
Consider a binary response \(Y\), where \(Y=1\) denotes the positive class and \(Y=0\) the negative class. For a predictor value \(x\), let \(p(x)=P(Y=1\mid x)\). In a boosted logistic model, the score \(F(x)\) is defined on the log-odds scale. The logistic loss for one observation is \(-[y\log p+(1-y)\log(1-p)]\); under the score convention below, minimizing this loss produces predictions on the probability scale through the logistic transformation.
A boosted model can update its score in stages. If the score before an update is \(F_{\mathrm{old}}(x)\) and the learner adds \(\Delta(x)\), then \(F_{\mathrm{new}}(x)=F_{\mathrm{old}}(x)+\Delta(x)\). For example, a tree can assign a different score increment to each terminal node. The increment is added to the old score; it is not added directly to the old probability.
Why the Logistic Transformation Works
The transformation follows directly from the definition of log odds. Starting with \(F=\log\{p/(1-p)\}\), exponentiation gives \(\exp(F)=p/(1-p)\). Multiplying by \(1-p\) and rearranging gives \(p=\exp(F)\{1-p\}\), so \(p\{1+\exp(F)\}=\exp(F)\). Dividing through gives the probability formula.
The same relationship explains the effect of a score update. The odds before the update are \(\exp(F_{\mathrm{old}})\). After adding \(\Delta\), the odds are \(\exp(F_{\mathrm{old}}+\Delta)=\exp(F_{\mathrm{old}})\exp(\Delta)\). Thus the update multiplies the odds by \(\exp(\Delta)\). It does not multiply the probability by that factor.
Subtracting \(p_{\mathrm{old}}\) from the expression for \(p_{\mathrm{new}}\) gives
For a positive increment, \(\exp(\Delta)>1\), so the probability increases; for a negative increment, it decreases. But an identical increment need not produce an identical probability change for different starting scores. The factor \(p_{\mathrm{old}}(1-p_{\mathrm{old}})\) and the denominator both depend on the starting probability.
Reading Score Updates on the Odds and Probability Scales
Worked Example: An Update That Doubles the Odds
A hypothetical claim classifier has a current boosted logistic score \(F_{\mathrm{old}}=\log(1/4)\). A new tree adds \(\Delta=\log 2\) for a particular claim. Find the old and new probabilities and describe the update. Use exact values, then report probabilities to four decimal places.
Method. Treat each score as log odds, convert the old score to odds, apply the multiplicative odds change, and then convert the new odds to a probability.
The old odds are \(\exp\{\log(1/4)\}=1/4\). Therefore the old probability is \( (1/4)/(1+1/4)=1/5=0.2000\).
The increment is \(\log 2\), so it multiplies the odds by \(\exp(\log 2)=2\). The new odds are \((1/4)(2)=1/2\). The new probability is \((1/2)/(1+1/2)=1/3=0.3333\). The change in probability is \(1/3-1/5=2/15=0.1333\).
Check. The new score is \(\log(1/4)+\log 2=\log(1/2)\), whose exponent is the new odds \(1/2\), as calculated. The update doubles the odds, but the probability does not double: twice \(0.2000\) would be \(0.4000\), not \(0.3333\). This method avoids treating the score increment as a direct probability increment.
A score increment can also be read as an odds multiplier in the opposite direction. An increment of \(-\log 3\), for example, multiplies the odds by \(1/3\). The corresponding probability change still depends on where the odds started.
Worked Example: Two Updates and Their Combined Effect
A hypothetical model starts with score \(F_0=\log(1/4)\) for a policyholder. Two successive tree updates are \(\Delta_1=\log 2\) and \(\Delta_2=-\log 3\). Find the probability after each stage and the total change from the starting probability. Report probabilities to four decimal places.
Method. Add the score increments, or equivalently multiply the odds by each update’s odds multiplier.
Initially, the odds are \(\exp(F_0)=1/4\), so \(p_0=(1/4)/(1+1/4)=1/5=0.2000\).
After the first update, the odds are \((1/4)\exp(\log 2)=(1/4)(2)=1/2\). Hence \(p_1=(1/2)/(1+1/2)=1/3=0.3333\).
The second update multiplies the odds by \(\exp(-\log 3)=1/3\). The final odds are \((1/2)(1/3)=1/6\), and the final probability is \(p_2=(1/6)/(1+1/6)=1/7=0.1429\). The total probability change is \(1/7-1/5=-2/35=-0.0571\).
Check. Adding the scores gives \(F_0+\Delta_1+\Delta_2=\log(1/4)+\log 2-\log 3=\log(1/6)\). Its exponent is the final odds \(1/6\), consistent with the sequential calculation. A common mistake is to add the two score increments to probabilities; updates are additive on the score scale, not on the probability scale.
Probability Estimation Is Not Classification
A probability estimate describes the model’s estimated chance of the positive class. A classification rule converts that estimate into a label by comparing it with a chosen threshold \(\tau\), where \(0<\tau<1\). Under the convention “classify positive when \(p\geq\tau\),” the threshold is applied after the probability has been calculated. The threshold does not change the probability estimate.
At \(\tau=0.5\), classifying as positive exactly when \(F\geq 0\) is equivalent to classifying as positive when \(p\geq 0.5\). For a different threshold, the equivalent score cutoff is \(\log\{\tau/(1-\tau)\}\). A threshold may be selected for a decision purpose, but it should not be confused with either the score or the estimated probability.
Worked Example: Applying a Nonstandard Classification Threshold
A hypothetical fraud-screening model gives a score \(F_{\mathrm{old}}=\log 2\) for a transaction. A new tree adds \(\Delta=\log 2\). The decision rule flags a transaction as positive when \(p\geq0.75\). Find the probabilities before and after the update and state the classifications. Report probabilities to four decimal places.
Method. Convert each score to odds and probability, then apply the stated threshold with its inclusive equality rule.
Before the update, the odds are \(\exp(\log 2)=2\), so \(p_{\mathrm{old}}=2/(1+2)=2/3=0.6667\). Since \(0.6667<0.75\), the transaction is classified negative.
After the update, the score is \(\log 2+\log 2=\log 4\). The odds are \(4\), giving \(p_{\mathrm{new}}=4/(1+4)=4/5=0.8000\). Since \(0.8000\geq0.75\), the transaction is classified positive. The probability increase is \(4/5-2/3=2/15=0.1333\).
Check. The score cutoff for the stated threshold is \(\log\{0.75/(1-0.75)\}=\log 3\). The old score \(\log 2\) is below this cutoff and the new score \(\log 4\) is above it, agreeing with the probability comparisons. Using zero as the cutoff would silently replace the stated threshold with \(0.5\).
Score Conventions and Common Traps
The logistic transformation is justified only when the score is defined on the log-odds scale. In particular, a raw score from a different boosting objective is not automatically a logit. AdaBoost’s exponential-loss margin, for instance, uses a score convention tied to labels coded as \(-1\) and \(+1\); applying the logistic transformation to such a score is not justified unless the model explicitly defines or calibrates it as a log-odds score. Check the score definition before converting it.
The logistic transformation also becomes less sensitive to score changes when the current probability is near zero or one. For a fixed small increment, a prediction near the middle of the probability scale can move more in absolute probability than a prediction already close to an endpoint. This is why reporting only a score increment, or only its odds multiplier, does not fully describe the change in estimated probability.
Confirm that the model’s score is defined as log odds for the positive class.
Add the learner’s increment to the existing score; do not add it to the probability.
Use \(p=1/\{1+\exp(-F)\}\), or convert through odds \(\exp(F)\).
Compare the probability with the stated threshold and report the class separately.
Keeping these stages separate prevents two related errors: interpreting an unrestricted real-valued score as a probability, and treating a threshold-based label as though it were the model’s probability estimate. The distinction is useful whenever a boosted model’s output is used both to quantify risk and to make a binary decision.
Check Your Understanding
For each problem, use the logistic log-odds convention unless the problem says otherwise.
- A hypothetical equipment-risk model has score \(F=\log 5\). Find the estimated positive-class probability. (Answer: \(5/6=0.8333\).)
- A starting probability is \(0.4\), and a learner adds \(\Delta=\log 3\). Find the new probability and the change from the starting probability. (Answer: new probability \(2/3=0.6667\); increase \(4/15=0.2667\).)
- A model starts at score \(\log(1/3)\) and receives two updates, \(\log 2\) and \(\log 3\). Find the final score’s odds and probability. (Answer: odds \(2\); probability \(2/3=0.6667\).)
- A model’s score is \(\log 4\), and the positive-class threshold is \(0.85\). State the probability and predicted class under the rule \(p\geq0.85\). (Answer: probability \(0.8000\); negative class.)
- A model starts at score \(0\), then receives an update of \(-\log 2\). Find the probability change and classification before and after under threshold \(\tau=0.4\), using \(p\geq\tau\) for the positive class. (Answer: probability falls from \(1/2\) to \(1/3\), a change of \(-1/6\); positive before and negative after.)