Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

full_state_update is not set in anomalib (Torchmetrics v0.9) #366

Closed
samet-akcay opened this issue Jun 13, 2022 · 0 comments · Fixed by #531
Closed

full_state_update is not set in anomalib (Torchmetrics v0.9) #366

samet-akcay opened this issue Jun 13, 2022 · 0 comments · Fixed by #531
Assignees
Labels
Metrics Metric Component.

Comments

@samet-akcay
Copy link
Contributor

full_state_update is not set, which has been introduced in Torchmetrics v0.9

Torchmetrics v0.9 introduced a new argument class property called full_state_update that has
not been set for this class (AdaptiveThreshold). The property determines if update by
default needs access to the full metric state. If this is not the case, significant speedups can be
achieved and we recommend setting this to False.
We provide an checking function
from torchmetrics.utilities import check_forward_no_full_state
that can be used to check if the full_state_update=True (old and potential slower behaviour,
default for now) or if full_state_update=False can be used safely.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Metrics Metric Component.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants