-
Notifications
You must be signed in to change notification settings - Fork 91
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 concerning temporal fusion #72
Comments
I don't think so since the data preparation doesn't involve can_bus info. Correct me if I am wrong, I am looking for the same point as well. |
Do you understand now?I don't think it's aligned, it's just concat |
I understand now.
Sent from Gmail Mobile
…On Mon, Mar 11, 2024 at 2:32 PM loserhou ***@***.***> wrote:
我不要这么认为,因为数据准备不涉及can_bus信息。如果我错了,请纠正我,我也在寻找同样的观点。
Do you understand now?I don't think it's aligned, it's just concat
—
Reply to this email directly, view it on GitHub
<#72 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AZQ6MVANMEDEKM7EMUDOUUTYXVFZHAVCNFSM6AAAAAA64XKEMGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSOBXG4YTONZTHE>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I understand that Fast-BEV uses 4 consecutive frames to improve performance. Do you correct the BEV features of the past frames before temporal fusion (concatenation)? I would naively think that some correction might be necessary to compensate for the ego-car motion between frames. Could you please guide me where this correction happens in the code?
Is it applied for every model or just for the larger ones?
The text was updated successfully, but these errors were encountered: