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

Unexpected label <num> #1

Open
aurooj opened this issue Oct 29, 2016 · 5 comments
Open

Unexpected label <num> #1

aurooj opened this issue Oct 29, 2016 · 5 comments

Comments

@aurooj
Copy link

aurooj commented Oct 29, 2016

Hi,

I am facing an issue which makes no sense to me. When I try to finetune deeplab on my dataset which has only 2 classes including background. I keep on getting this error. I tried changing ignore_label value but it doesn't help, so I kept that to 255.

Any hints what causes this error to pop up?

Also, in deeplab's older version, we could add weight_source file to loss layer if our classes are unbalanced. But I checked into updated softmax_loss_layer.cpp, this parameter is not being handled anymore. Any specific reasons for omitting it? Also, what is the work around to penalize for class which has few pixels?

Any help will be highly appreciated!
Thanks.

@aurooj
Copy link
Author

aurooj commented Nov 2, 2016

Okay, so I tried printing out the labels it takes from my image and what goes inside seg_accuracy_layer.cpp and figured out that, for some reason, it changes my actual label value which is 1 to 38 during interpolation.

Can anyone please explain me what can be the possible reason? I am sorry if I am making some obvious mistake here, but I will appreciate if anyone points it out to me.

Thanks in advance!

@ajdroid
Copy link

ajdroid commented Jan 10, 2017

Did you figure this out, @aurooj ?

@aurooj
Copy link
Author

aurooj commented Jan 10, 2017

I couldn't resolve this issue. But since the issue was just in SegAccuracy layer, I replaced this layer with Accuracy layer, and then everything worked fine for me.

@ajdroid
Copy link

ajdroid commented Jan 12, 2017

Hmm, that works but I'm still curious as to what causes this.

@aurooj
Copy link
Author

aurooj commented Jan 13, 2017

Yes, I think it should be a bug since many people are reporting this issue.

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