-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
Retrieve Predictions: Prediction score
missing
#7151
Comments
This behavior isn’t caused by the task format template “shadowing” the score field. In Label Studio, the Data Manager calculates a field called “predictions_score” by aggregating prediction scores filtered by the project’s model version. In your case, when you test the model connection directly, the response (with score) is as expected; however, when using the action from the project page, the score is coming up as null because the system is only considering predictions whose “model_version” matches the project’s value. A couple of things to check:
Thank you,
|
Hello, Under the predictions tab, do you see different predictions there? Thank you,
|
When connecting a model and testing it, I get a
with the score showing in the response.
However, when I use the feature from a project's page (select tasks and use action
Retrieve Predictions
), I get something like thisThe fields
Prediction results
andPrediction model versions
are populated, but notPrediction score
.Is it because somehow it uses this template (https://labelstud.io/guide/task_format) for predictions, and shadows the score field? In fact in the JSON properties, there is mention of
prediction.score
, but is not present on the template.Here is some more info from the network flow inspector:
Payload request and response from
/api/dm/actionsid=retrieve_tasks_predictions&tabID=239&project=79
Payload response from
api/tasks?page=1&page_size=30&view=239&project=79
The "predictions_score" is set to
null
.Environment (please complete the following information):
The text was updated successfully, but these errors were encountered: