Compute the MultilabelPrecision metric — provided by torchmetrics. Use when the user has predictions and ground-truth and needs to compute MultilabelPrecision, or asks how to score with MultilabelPrecision.
Scanned 9/11/2026
Install to Claude Code
npx -y skills add qhjqhj00/research-skills-pool --skill multilabelprecision --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Multilabelprecision?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/qhjqhj00-multilabelprecision)More formats (shields.io, HTML) on the badges page.
---
name: multilabelprecision
description: Compute the MultilabelPrecision metric — provided by torchmetrics. Use when the user has predictions and ground-truth and needs to compute MultilabelPrecision, or asks how to score with MultilabelPrecision.
metadata:
skill_kind: metric
source_lib: torchmetrics
import_path: torchmetrics.classification.MultilabelPrecision
source: library_introspection
---
# multilabelprecision
> Metric `MultilabelPrecision` from `torchmetrics` (torchmetrics.classification.MultilabelPrecision)
## When to invoke this skill
The user has predictions + ground truth and asks to evaluate with MultilabelPrecision, or
mentions `torchmetrics.classification.MultilabelPrecision` directly, or wants the standard torchmetrics implementation.
## Reference signature
```python
from torchmetrics.classification import MultilabelPrecision
# MultilabelPrecision(num_labels: int, threshold: float = 0.5, average: Optional[Literal['micro', 'macro', 'weighted', 'none']] = 'macro', multidim_average: Literal['global', 'samplewise'] = 'global', ignore_index: Optional[int] = None, validate_args: bool = True, **kwargs: Any) -> None
```
## Library docstring
```
Compute `Precision`_ for multilabel tasks.
.. math:: \text{Precision} = \frac{\text{TP}}{\text{TP} + \text{FP}}
Where :math:`\text{TP}` and :math:`\text{FP}` represent the number of true positives and false positives
respectively. The metric is only proper defined when :math:`\text{TP} + \text{FP} \neq 0`. If this case is
encountered for any label, the metric for that label will be set to `zero_division` (0 or 1, default is 0) and
the overall metric may therefore be affected in turn.
As input to ``forward`` and ``update`` the metric accepts the following input:
- ``preds`` (:class:`~torch.Tensor`): An int tensor or float tensor of shape ``(N, C, ...)``.
If preds is a floating point tensor with values outside [0,1] range we consider the input to be logits and
will auto apply sigmoid per element. Additionally, we convert to int tensor with thresholding using the value
in ``threshold``.
- ``target`` (:class:`~torch.Tensor`): An int tensor of shape ``(N, C, ...)``.
As output to ``forward`` and ``compute`` the metric returns the following output:
- ``mlp`` (:class:`~torch.Tensor`): The returned shape depends on the ``average`` and ``multidim_average``
arguments:
- If ``multidim_average`` is set to ``global``:
- If ``average='micro'/'macro'/'weighted'``, the output will be a scalar tensor
- If ``average=None/'none'``, the shape will be ``(C,)``
- If ``multidim_average`` is set to ``samplewise``:
- If ``average='micro'/'macro'/'weighted'``, the shape will be ``(N,)``
- If ``average=None/'none'``, the shape will be ``(N, C)``
If ``multidim_average`` is set to ``samplewise`` we expect at least one additional dimension ``...`` to be present,
which the reduction will then be applied over instead of the sample dimension ``N``.
Args:
num_labels: Integer specifying the number of labels
threshold: Threshold for transforming probability to binary (0,1) predictions
average:
Defines the reduction that is applied over labels. Should be one of the following:
- ``micro``: Sum statistics over all labels
- ``macro``: Calculate statistics for each label and average them
- ``weighted``: calc
```
## Quick recipe
```python
import torchmetrics.classification as _m
score = _m.MultilabelPrecision(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!