Replies: 1 comment
-
Hi, Here is the code, I use to check the time:
One option you could consider is the use of a separate thread for computing the trajectory. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi,
We have a question about the computation time constraint.
We submit our agent to the cloud server. The result shows that our agent violated the computation time constraint many times(400 for hit-task and 700 for defend-task.)
But when we test our agent locally, this is not the case(the number of computation time violations is under 100 for both tasks.)
We only use the CPU to evaluate the agent. The CPU is Intel Core i7-7700HQ.
May I ask what could be the possible reason for the huge difference?
If it is due to the different hardware, what type of CPU is used in the cloud server?
Another question, when I built the docker image according to the documentation of the challenge, I just ignored installing the NVIDIA Container Toolkit. But I can still build the image, test the evaluation locally and submit the agent to the cloud.
Is this toolkit important for the evaluation? Could this be the reason for the increased computation time?
Beta Was this translation helpful? Give feedback.
All reactions