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

Why is decoder_input of size 3 ? #17

Open
ashishkr23 opened this issue Feb 9, 2021 · 1 comment
Open

Why is decoder_input of size 3 ? #17

ashishkr23 opened this issue Feb 9, 2021 · 1 comment

Comments

@ashishkr23
Copy link

ashishkr23 commented Feb 9, 2021

Hi

Thanks for the code and the paper. Awesome work :)

While initialising the individualTF model why does the decoder_input/decoder_output have size 3 whereas the the encoder_input size is 2. Hence the ouput of the decoder is of the shape [N,Steps,3]. What is the third value we are trying to predict per step ? I was assuming we are trying to predict only the relative displacements in the cartesian coordinates ?
Also what does the extra term in the loss signify ? torch.mean(torch.abs(pred[:,:,2])

Would be great if you could clarify this doubt.

Thanks

@BYZANTINE26
Copy link

Hi

Thanks for the code and the paper. Awesome work :)

While initialising the individualTF model why does the decoder_input/decoder_output have size 3 whereas the the encoder_input size is 2. Hence the ouput of the decoder is of the shape [N,Steps,3]. What is the third value we are trying to predict per step ? I was assuming we are trying to predict only the relative displacements in the cartesian coordinates ?
Also what does the extra term in the loss signify ? torch.mean(torch.abs(pred[:,:,2])

Would be great if you could clarify this doubt.

Thanks

did you figured this out ?

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