-
Notifications
You must be signed in to change notification settings - Fork 69
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
Unable to use the fast agent #23
Comments
I tried to convert the torch model into TorchScript by myself. The model was successfully loaded but the agent performance is not improved. I use the following code to convert brake prediction model and segmentation model into TorchScript.
It shows several warnings but no errors. I wonder if I am correct or I just missed something important? |
Thanks for reporting this! Could you try again the default .pt files (updated) at your convenience? |
Hello, the following error occurs with updated .pt files.
Do you use multiple cards in your setup? In my setup, the default agent has nearly 0.6 simulation ratio but fast agent has ratio below 0.5 Maybe the new CPU is strong enough to handle the point painting task. |
Could you try this command and see if it works? I just tried this on my setup and it works
Compared to the default agent (sim/real ~ 0.15x) the fast agent I see with my setup is usually above 0.22x (to 0.25x depending on routes). I am not using multiple cards here for inference. Curious to see if wrapping |
Error occurs
You choose the second GPU on your machine with |
Oops forgot to remove the CUDA_VISIBLE_DEVICES= part in the command. Could you run it with CUDA_VISIBLE_DEVICES="0"? The torch script jit is saved to device "cuda" in a script with specified CUDA_VISIBLE_DEVICES to one gpu, so I am pretty sure it will work... |
Still with the error I have also tried the TorchScript converted by myself, it works. So I wonder if it is caused by the difference of the devices (3080Ti vs Titan Xp) |
What python and pytorch+cuda versions are you using? |
|
Thanks for the info! My guess then is that the pytorch versions might have caused the discrepancy, the .pt trace file was created with pytorch |
how to produce such |
I didn't find the diff between v2 and v1 agent training scripts. Is that mean the two version models can use together? for example, just use v1 model on v2 also fine? ( forget this one. Since it has different on model scripts, it should not use the v1 on v2; through config v2, only |
Hello! The training scripts are different for the bev and full lidar agent (segmentation is identical, the brake model has a different architecture). I'm working on cleaning them up for release, thanks! |
Sorry for the delay, let me know if you have run into any issues running the codes! |
hello.I also encountered a problem with agent. After running, it displays:Could not set up the required agent:
|
Traceback (most recent call last): |
Hello, thanks for the open source of this fantastic work!
I am able to use the default v2 agent. However, I encounter such error when use the fast agent.
Could you please help me to solve this problem?
The text was updated successfully, but these errors were encountered: