Skip to content
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

details about the embedding dimension #3

Closed
Yisten opened this issue May 19, 2021 · 7 comments
Closed

details about the embedding dimension #3

Yisten opened this issue May 19, 2021 · 7 comments

Comments

@Yisten
Copy link

Yisten commented May 19, 2021

Could you provide the the embedding dimension of each step in motion aggregator and map extractor( with VectorNet)? I haven't found them or correponding reference in Implementation Details in Appendix. Are they same with the hidden state(128)?

@Yisten
Copy link
Author

Yisten commented May 19, 2021

Additionally, could you tell more about the comsumption of the graphic memory when doing inference? It will help me a lot.

@Mrmoore98
Copy link
Collaborator

Could you provide the the embedding dimension of each step in motion aggregator and map extractor( with VectorNet)? I haven't found them or correponding reference in Implementation Details in Appendix. Are they same with the hidden state(128)?

Yes, all the hidden feature have the same dimensional size(128)
And the implementation of VectorNet you can refer to this repo. We use the vector net to encode each lane vector set into a 128-dimensional vector.

@Mrmoore98
Copy link
Collaborator

Additionally, could you tell more about the comsumption of the graphic memory when doing inference? It will help me a lot.

In my implementation, the comsumption of the GPU at inference stage is 3998MiB when the batchsize is 64. I use GTX 1660 to get this result.

@Yisten
Copy link
Author

Yisten commented May 24, 2021

Thanks for your reply and it is very informative!
One more question about initialization, please.
Is Xaiver enough? Had you pretrained the vectornet before compound training? If yes, how?

@Mrmoore98
Copy link
Collaborator

Thanks for your reply and it is very informative!
One more question about initialization, please.
Is Xaiver enough? Had you pretrained the vectornet before compound training? If yes, how?

All the componets in mmTransformer are trained from scratch. You can try different initialization methods. This initialization method is inherited from the aforementioned repo.

FYI, all the weights are initialized with Xaiver, except for the trajectory proposals, which are initialized with orthogonalize initilization.

@Yisten
Copy link
Author

Yisten commented May 24, 2021

Got it! Thanks for your patience and have a nice day XD

@Mrmoore98
Copy link
Collaborator

If you have further problems about reproduction, feel free to open a new issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants