You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thanks for the great works! And I wonder how to calculate VTSS for user-provided videos?
The official VTSS inference demo needs the ground truth labels to resize predicted labels to the same scale as ground truth labels (pr_labels = rescale(pr_labels, gt_labels), line 83, training_suitability_assessment/inference.py). However, user-provided videos do not have the ground truth values. I have noticed the No Label Testing part in FusionDataset class (datasets.py), but the method simply set the gt_label to -1, after rescale() all the predicted values will be set to -1.
Thank you for your time and assistance!
The text was updated successfully, but these errors were encountered:
Thank you for your question, in the code, if gt_label is set to -1, the predicted result will not be scaled, i.e. it will be a score between 0 and 1, and you can scale the value in any way you want.
I estimated the distribution of the gt_labels using Figure 6 from the paper, and it was able to obtain similar results. Here are the estimations I used:
I also tried outputting the results without re-scaling, which ranged approximately from -0.05 to 0.068. I'm curious if this range aligns with your results.
Thanks for the great works! And I wonder how to calculate VTSS for user-provided videos?
The official VTSS inference demo needs the ground truth labels to resize predicted labels to the same scale as ground truth labels (
pr_labels = rescale(pr_labels, gt_labels)
, line 83, training_suitability_assessment/inference.py). However, user-provided videos do not have the ground truth values. I have noticed theNo Label Testing
part inFusionDataset
class (datasets.py
), but the method simply set the gt_label to -1, afterrescale()
all the predicted values will be set to -1.Thank you for your time and assistance!
The text was updated successfully, but these errors were encountered: