-
Notifications
You must be signed in to change notification settings - Fork 13
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
SLIC #4
Comments
I believe SLIC does only guarantee equal number of superpixels in the |
Yes!I just try it. They can get the equal number of superpixels when set it to false. But the number of superpixels obtained is not equal to the 'num_segments=100' (I just set the parameter). |
So you have equal number of superpixels, but there are less than |
Yes! And when the 'num_segments=100', the equal number of superpixels is 121 more than 100. |
I am not really sure, sorry. Maybe you can consult the |
OK! Thank you very much! |
Is this code a Splineconv model? Sorry, I am not familiar with this code and Splineconv. |
Not really, it is my masters thesis. You can find the SplineConv implementation here. |
I try use' embedded_gcnn code' to get the cifar10 dataset. And I modified it to the 'pytorch_geometric dataset' format. Then I run the mnist_graculs.py (loading the cifar10 dataset) and the result is just about 0.43. Maybe I was wrong. Could you give some advices? |
This is actually quite hard to say. It could be anything from wrong data handling to bad hyperparameters. |
while num_left > 0:
The above is the code I modified after dataset.py. In order to be able to change the data format of pytorch-geometric, I feel that there should be no big problem. |
Hi! Amazing work!
When using a algorithm such as SLIC to obtain a super pixel block, it seems that the super pixel block of each picture is different. And the number of obtained super pixel blocks is not equal to the value set by the parameter "num_segments".
I can not understand it!
The text was updated successfully, but these errors were encountered: