Compute the BinarySensitivityAtSpecificity metric — provided by torchmetrics. Use when the user has predictions and ground-truth and needs to compute BinarySensitivityAtSpecificity, or asks how to score with BinarySensitivityAtSpecificity.
Scanned 9/11/2026
Install to Claude Code
npx -y skills add qhjqhj00/research-skills-pool --skill binarysensitivityatspecificity --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Binarysensitivityatspecificity?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/qhjqhj00-binarysensitivityatspecificity)More formats (shields.io, HTML) on the badges page.
---
name: binarysensitivityatspecificity
description: Compute the BinarySensitivityAtSpecificity metric — provided by torchmetrics. Use when the user has predictions and ground-truth and needs to compute BinarySensitivityAtSpecificity, or asks how to score with BinarySensitivityAtSpecificity.
metadata:
skill_kind: metric
source_lib: torchmetrics
import_path: torchmetrics.classification.BinarySensitivityAtSpecificity
source: library_introspection
---
# binarysensitivityatspecificity
> Metric `BinarySensitivityAtSpecificity` from `torchmetrics` (torchmetrics.classification.BinarySensitivityAtSpecificity)
## When to invoke this skill
The user has predictions + ground truth and asks to evaluate with BinarySensitivityAtSpecificity, or
mentions `torchmetrics.classification.BinarySensitivityAtSpecificity` directly, or wants the standard torchmetrics implementation.
## Reference signature
```python
from torchmetrics.classification import BinarySensitivityAtSpecificity
# BinarySensitivityAtSpecificity(min_specificity: float, thresholds: Union[int, list[float], torch.Tensor, NoneType] = None, ignore_index: Optional[int] = None, validate_args: bool = True, **kwargs: Any) -> None
```
## Library docstring
```
Compute the highest possible sensitivity value given the minimum specificity thresholds provided.
This is done by first calculating the Receiver Operating Characteristic (ROC) curve for different thresholds and the
find the sensitivity for a given specificity level.
Accepts the following input tensors:
- ``preds`` (float tensor): ``(N, ...)``. Preds should be a tensor containing probabilities or logits for each
observation. If preds has values outside [0,1] range we consider the input to be logits and will auto apply
sigmoid per element.
- ``target`` (int tensor): ``(N, ...)``. Target should be a tensor containing ground truth labels, and therefore
only contain {0,1} values (except if `ignore_index` is specified).
Additional dimension ``...`` will be flattened into the batch dimension.
The implementation both supports calculating the metric in a non-binned but accurate version and a binned version
that is less accurate but more memory efficient. Setting the `thresholds` argument to `None` will activate the
non-binned version that uses memory of size :math:`\mathcal{O}(n_{samples})` whereas setting the `thresholds`
argument to either an integer, list or a 1d tensor will use a binned version that uses memory of
size :math:`\mathcal{O}(n_{thresholds})` (constant memory).
Args:
min_specificity: float value specifying minimum specificity threshold.
thresholds:
Can be one of:
- ``None``, will use a non-binned approach where thresholds are dynamically calculated from
all the data. It is the most accurate but also the most memory-consuming approach.
- ``int`` (larger than 1), will use that number of thresholds linearly spaced from
0 to 1 as bins for the calculation.
- ``list`` of floats, will use the indicated thresholds in the list as bins for the calculation
- 1d ``tensor`` of floats, will use the indicated thresholds in the tensor as
bins for the calculation.
validate_args: bool indicating if input arguments and tensors should be validated for correctness.
Set to ``False`` for faster computations.
kwargs: Additional keyword arguments, see :ref:`Metric kwargs`
```
## Quick recipe
```python
import torchmetrics.classification as _m
score = _m.BinarySensitivityAtSpecificity(y_true, y_pred)
```
## Don'ts
- Don't reimplement when the library version handles edge cases (NaN, ties, empty inputs) better than a hand-rolled formula.
- Always check the library version's argument order — sklearn is `(y_true, y_pred)` while torchmetrics is `(preds, target)`.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!