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

The connection weights don't seem to be related to image features #9

Closed
trisct opened this issue Nov 20, 2020 · 3 comments
Closed

The connection weights don't seem to be related to image features #9

trisct opened this issue Nov 20, 2020 · 3 comments

Comments

@trisct
Copy link

trisct commented Nov 20, 2020

It seems that in your code the connection weights are stored as parameters of the generator module. They don't seem to be related to image features, which means at inference, the network uses the same connection weights for all images. Wouldn't this limit the network's ability to handle different images?

@czq142857
Copy link
Owner

Yes. For different images, the only difference in the BSP-trees is the plane parameters. The connections are the same. It may limit the network's capacity. The concern is that the size of the connection matrix T is pxc, where p is the number of planes and c the number of convexes. In our implementation, p=4,096 and c=256, therefore pxc=1,048,576. It is hard to output those weights without reducing p or c.

@trisct
Copy link
Author

trisct commented Nov 21, 2020

Thanks for the clarification. I wonder if you have done any experiment to see if outputting the weights from image features is possible in simple cases, for example, the 2d toy problems.

@czq142857
Copy link
Owner

No, I haven't.

@trisct trisct closed this as completed Nov 21, 2020
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