You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
LAM is an excellent work, and I am grateful for the contributions your team has made to the community!
I have a question regarding the ModelLAM class in your codebase, specifically about the attribute latent_query_points_type. I noticed that this attribute can be set to either "embedding" or "e2e_flame". From my understanding, "embedding" assigns each FLAME vertex its own learnable embedding, while "e2e_flame" assigns an embedding based on the point's coordinates. Could you please explain why "e2e_flame" was chosen over "embedding"? I did not find this detail discussed in the paper, and I would greatly appreciate any insights you can provide on this decision.
Thanks for your interest in our work. The learnable point embedding can be implemented by "nn.Embedding" or positional embedding with learnable MLP. We use the latter one in the released code. We also mention this in the paragraph above Forumlar (1) in our paper. Using "nn.Embedding" also gets good results.
LAM is an excellent work, and I am grateful for the contributions your team has made to the community!
I have a question regarding the
ModelLAM
class in your codebase, specifically about the attributelatent_query_points_type
. I noticed that this attribute can be set to either "embedding" or "e2e_flame". From my understanding, "embedding" assigns each FLAME vertex its own learnable embedding, while "e2e_flame" assigns an embedding based on the point's coordinates. Could you please explain why "e2e_flame" was chosen over "embedding"? I did not find this detail discussed in the paper, and I would greatly appreciate any insights you can provide on this decision.The text was updated successfully, but these errors were encountered: