waymo-open-dataset icon indicating copy to clipboard operation
waymo-open-dataset copied to clipboard

INVALID_ARGUMENT: Duplicate prediction scenario ID found :xxxxx

Open 786739982 opened this issue 1 year ago • 4 comments

Hello!After submitting the trajectory prediction results, it was dispalyed “INVALID_ARGUMENT: Duplicate prediction scenario ID found :xxxxx” . I found that the same scene does appear multiple times in my submission results, but although it is the same scene, the “object_id” of the same scene is different every time it appears. May I know how to solve this problem ?

Thank you very much!!!

786739982 avatar Oct 13 '23 03:10 786739982

Hi, Each example record has a unique ID in the scenario_id field. Each example should only have one ChallengeScenarioPredictions entry in the scenario_predictions field within the MotionChallengeSubmission proto. Predictions for all objects in that scenario should be included in the single ChallengeScenarioPredictions proto. If the entry appears twice this will return this error. Can you describe how you generate the submission such that there are multiple entries with the same scenario_id value?

scott-ettinger avatar Oct 18 '23 21:10 scott-ettinger

Firstly, I generated the result.pkl file using the validation set. Then I found out that there are 44097 prediction results in the result.pkl file, each with a different object_ id, but their scenario_ id may be the same. This also means that a scenario may correspond to the predicted results of multiple objects. So there will be duplicate scenario_id in the 44097 predicted results. Then I converted 44097 results into 44097 'repeated ChallengeScenarioPredictions scenario_predictions' fields. And then I reported the current error. Later, I modified the submission method by placing the same scenes from 44097 results in the same 'repeated ChallengeScenarioPredictions scenario_predictions' field, and then displaying the error' INVALID_ARGUMENT: Not enough scenario predictions in submission: 10084 ' May I ask where my problem lies? How to solve it? Thank you very much!

786739982 avatar Oct 19 '23 03:10 786739982

Hello, Firstly, I generated the result.pkl file using the validation set. Then I found out that there are 44097 prediction results in the result.pkl file, each with a different object_ id, but their scenario_ id may be the same. This also means that a scenario may correspond to the predicted results of multiple objects. So there will be duplicate scenario_id in the 44097 predicted results. Then I converted 44097 results into 44097 'repeated ChallengeScenarioPredictions scenario_predictions' fields. And then I reported the current error. Later, I modified the submission method by placing the same scenario from 44097 results in the same 'repeated ChallengeScenarioPredictions scenario_predictions' field, and then displaying the error' INVALID_ARGUMENT: Not enough scenario predictions in submission: 10084 ' May I ask where my problem lies? How to solve it?

Thank you very much!

(My code has been added in the attachment)

朱泓睿 @.***

 

------------------ 原始邮件 ------------------ 发件人: "waymo-research/waymo-open-dataset" @.>; 发送时间: 2023年10月19日(星期四) 凌晨5:26 @.>; @.@.>; 主题: Re: [waymo-research/waymo-open-dataset] INVALID_ARGUMENT: Duplicate prediction scenario ID found :xxxxx (Issue #729)

Hi, Each example record has a unique ID in the scenario_id field. Each example should only have one ChallengeScenarioPredictions entry in the scenario_predictions field within the MotionChallengeSubmission proto. Predictions for all objects in that scenario should be included in the single ChallengeScenarioPredictions proto. If the entry appears twice this will return this error. Can you describe how you generate the submission such that there are multiple entries with the same scenario_id value?

— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: @.***>

786739982 avatar Oct 19 '23 03:10 786739982

I'm not sure I understand your comments about duplicate scenario IDs. Each scenario has a unique scenario ID. For each scenario there should be only one entry in the scenario_predictions field of the submission that includes predictions for all objects in that scenario.

scott-ettinger avatar Oct 31 '23 05:10 scott-ettinger