-
Notifications
You must be signed in to change notification settings - Fork 405
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
Add Support for SQ and RQ in Panoptic Quality #2380
Comments
Hi! thanks for your contribution!, great first issue! |
Hi @ChristophReich1996, thanks for raising this issue. |
Hi @SkafteNicki, we could just use the already computed IoU, TP, FN, and FP to also compute both SQ and RQ. We can just follow the equation from the original paper: We would just need to change this function: torchmetrics/src/torchmetrics/functional/detection/_panoptic_quality_common.py Lines 447 to 469 in afae59e
Additionally, it was already discussed somewhere, but I guess it would be beneficial to compute PQ, SQ, and RQ on a per-class level as well as the global average. |
@ChristophReich1996 thanks for the info. Yeah that should be pretty easy to add/modify in the current codebase. Only thing to consider is how we should go about backwards compatibility. I agree that it does not make sense to separate out the individual scores into different metrics. |
@SkafteNicki Yeah backward compatibility could be somewhat cumbersome. But I guess having some flag could get us backward compatibility. Let me quickly draft a pull request. |
🚀 Feature
First of all thanks for implementing the Panoptic Quality (PQ) metric. However, the current PQ implementation only computes the PQ. The Segmentation Quality (SQ) and Recognition Quality (RQ) are not computed. It would be amazing to have an option to also compute these metrics within the PQ implementation.
Motivation
Almost all papers (e.g., U2Seg) report the PQ alongside SQ and RQ so extending the PQ implementation to also compute SQ and RQ would be amazing.
Alternatives
We could also implement both SQ and RQ as separate metrics, however, since I'm not aware of any work reporting SQ or RQ w/o PQ this would be somewhat inconvenient. This would also lead to an additional compute overhead.
The text was updated successfully, but these errors were encountered: