Compute the BinaryPrecisionAtFixedRecall metric — provided by torchmetrics. Use when the user has predictions and ground-truth and needs to compute BinaryPrecisionAtFixedRecall, or asks how to score with BinaryPrecisionAtFixedRecall.
Scanned 9/11/2026
Install to Claude Code
npx -y skills add qhjqhj00/research-skills-pool --skill binaryprecisionatfixedrecall --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Binaryprecisionatfixedrecall?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/qhjqhj00-binaryprecisionatfixedrecall)More formats (shields.io, HTML) on the badges page.
---
name: binaryprecisionatfixedrecall
description: Compute the BinaryPrecisionAtFixedRecall metric — provided by torchmetrics. Use when the user has predictions and ground-truth and needs to compute BinaryPrecisionAtFixedRecall, or asks how to score with BinaryPrecisionAtFixedRecall.
metadata:
skill_kind: metric
source_lib: torchmetrics
import_path: torchmetrics.classification.BinaryPrecisionAtFixedRecall
source: library_introspection
---
# binaryprecisionatfixedrecall
> Metric `BinaryPrecisionAtFixedRecall` from `torchmetrics` (torchmetrics.classification.BinaryPrecisionAtFixedRecall)
## When to invoke this skill
The user has predictions + ground truth and asks to evaluate with BinaryPrecisionAtFixedRecall, or
mentions `torchmetrics.classification.BinaryPrecisionAtFixedRecall` directly, or wants the standard torchmetrics implementation.
## Reference signature
```python
from torchmetrics.classification import BinaryPrecisionAtFixedRecall
# BinaryPrecisionAtFixedRecall(min_recall: 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 precision value given the minimum recall thresholds provided.
This is done by first calculating the precision-recall curve for different thresholds and the find the precision for
a given recall level.
As input to ``forward`` and ``update`` the metric accepts the following input:
- ``preds`` (:class:`~torch.Tensor`): A float tensor of shape ``(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`` (:class:`~torch.Tensor`): An int tensor of shape ``(N, ...)``. Target should be a tensor containing
ground truth labels, and therefore only contain {0,1} values (except if `ignore_index` is specified). The value
1 always encodes the positive class.
.. tip::
Additional dimension ``...`` will be flattened into the batch dimension.
As output to ``forward`` and ``compute`` the metric returns the following output:
- ``precision`` (:class:`~torch.Tensor`): A scalar tensor with the maximum precision for the given recall level
- ``threshold`` (:class:`~torch.Tensor`): A scalar tensor with the corresponding threshold level
.. note::
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_recall: float value specifying minimum recall threshold.
thresholds:
Can be one of:
- If set to ``None``, will use a non-binned approach where thresholds are dynamically calculated from
all the data. Most accurate but also most memory consuming approach.
- If set to an ``int`` (larger than 1), will use that number of thresholds linearly spaced from
0 to 1 as bins for the calcul
```
## Quick recipe
```python
import torchmetrics.classification as _m
score = _m.BinaryPrecisionAtFixedRecall(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!