-
Notifications
You must be signed in to change notification settings - Fork 136
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
Question for Submitting the ml planner from #306 #308
Comments
I meet the same question. I did |
same question seems, don't know how to fix it. |
This is the error during initialization:
|
What is your team name and time of submission? I can look up the detailed logs for you |
Hi, my team name is changdrive. Thank you very much! |
Hi @patk-motional, Same problem here, the submitted file is {"submitted_image_uri": "937891341272.dkr.ecr.us-east-1.amazonaws.com/nuplan-planning-challenge-1856-participant-team-16281:6095e0da-394d-4c89-8e37-159cc30b67fc"}, could you please find detailed logs for me? Thanks a lot. |
Hi, @patk-motional,We have also encountered a similar problem. We followed the tutorial and used the To troubleshoot this, we added an "ls" command to check if the ckpt file is present in the nuplan-devkit folder. The result showed that the file does exist. It is worth noting that we were able to successfully run the simple planner. Here are some of our configurations. Dockerfile & Dockerfile.submission entrtpoint_submission.sh & entrtpoint_simulation.sh ml_planner.yaml Here is the output of the ls command executed in the entrypoint_simulation.sh script Following that, the command |
@MMz000, the The error is because you are looking for |
There are no detailed logs for you as your container failed to start. |
Your hydra config isn't setup properly
|
My submission file is {"submitted_image_uri": "937891341272.dkr.ecr.us-east-1.amazonaws.com/nuplan-planning-challenge-1856-participant-team-20999:92e91991-f365-46b5-9493-acfa2dd57e96"} I did docker-compose up --build and it success in my local server. |
Hi @abbyxxn, I only see logs for the initialization stage. This usually indicates that your planner timed out in the first iteration. Have you profiled your planner locally?
|
Thank you for your very useful reply! May I know the detailed error message? |
@abbyxxn do you mean logs from your container? I see many prints like this (this one is the last one, most are around 0.89 in time consumed)
|
Can I ask about my error logs for my submissions for team
I tried the following syntax: Submitted at May 25, 2023 11:50:58 AM
Submitted at May 25, 2023 1:26:01 PM
Submitted at May 25, 2023 2:33:31 PM
|
Thank you for your prompt response. But this is an old submission from last night, before I included the huggingface/timm cache into |
This was from your latest submission |
@patk-motional Would you mind sharing the error log of my two latest two submissions? One of them I downgraded |
@tinkei Can you share the |
@tinkei one problem is definitely you commenting out this line: |
@patk-motional I am getting the exact same error: #308 (comment) . My submission details are: |
I've pushed to your stderr |
Hi, the following is the error:
for these errors, where do you think we need to make changes, so that error can be resolved? Where should we set the HYDRA_FULL_ERROR=1 ? In entrypoint_submission.sh, we have the following line:
|
Thanks! Everything is working now! |
@sindhu-pr |
I met this problem too. Actually I have success to profile my planner locally but still get this problems. Then I notice this #298 .As i use nuplan-devkit v1.1, the Dockerfile.submmission is still on laste version. I follow #298 to update Dockerfile.submmission manually, then submit and get so there must be some problem if you use last version of Dockerfile.submmission. you can fix it through #298 |
Hi this question is still the question from #306. I did exactly as you told us in #302, but it still failed. I wonder what should i put in checkpoint_path? I checked my docker images files, my model.ckpt is indeed in the nuplan-devkit. I don't know what did I miss. thanks!
The text was updated successfully, but these errors were encountered: