We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I observed that in code SDEModel3Dto2D_node_adj_dense_02, loss is calculated by: losses_x = torch.square(score_x + z_x) # [B, max_num_nodes, num_class_X] or [B, max_num_nodes, 1] losses_adj = torch.square(score_adj + z_adj) # [B, max_num_nodes, max_num_nodes]
But in SDE_model_2d_to_3d, the code to calculate loss is loss_pos = torch.sum((scores - pos_noise) ** 2, -1) # (num_node)
I'm confused why the 3D_to_2D code isn't score - x.
The text was updated successfully, but these errors were encountered:
Hi @MorningEatDinner I am not sure what you mean by why the 3D_to_2D code isn't score - x. Can you explain this further?
why the 3D_to_2D code isn't score - x
Sorry, something went wrong.
No branches or pull requests
I observed that in code SDEModel3Dto2D_node_adj_dense_02, loss is calculated by:
losses_x = torch.square(score_x + z_x) # [B, max_num_nodes, num_class_X] or [B, max_num_nodes, 1]
losses_adj = torch.square(score_adj + z_adj) # [B, max_num_nodes, max_num_nodes]
But in SDE_model_2d_to_3d, the code to calculate loss is
loss_pos = torch.sum((scores - pos_noise) ** 2, -1) # (num_node)
I'm confused why the 3D_to_2D code isn't score - x.
The text was updated successfully, but these errors were encountered: