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

Question about processing of the MNIST-example #2

Open
RoelvH opened this issue Mar 4, 2022 · 1 comment
Open

Question about processing of the MNIST-example #2

RoelvH opened this issue Mar 4, 2022 · 1 comment

Comments

@RoelvH
Copy link

RoelvH commented Mar 4, 2022

Thank you for the interesting code!

I had a question regarding the MNIST example present in your paper, as I do not completely follow here and it is not found in the Git. As opposed to the FAUST dataset where we are dealing purely with shapes, I guess that MNIST is transformed to lie on a rough grid so that we have two types of information, namely the features belonging to a node (in this case the raw pixel value, or "data.x") and the position in 3D for each node ("data.pos" so to speak). Am I interpreting it right when I say that the gauge-equivariant mesh convolutions are based on the information found in "pos", while they are applied to the raw pixel values?

Thanks in advance!

@pimdehaan-qc
Copy link

You're right in that we didn't include that code in this release, as we thought it'd be of limited value to others. You're also right in that interpretation. The positions affect the kernel values, but the input features to the network are only the pixel values.

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