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

Error in LRRAddMasking #4

Closed
JoelChev opened this issue Nov 21, 2016 · 5 comments
Closed

Error in LRRAddMasking #4

JoelChev opened this issue Nov 21, 2016 · 5 comments

Comments

@JoelChev
Copy link

Hi, I'm trying to run the demo LRR4XTrainVGG16Pascal.m code on the Pascal dataset. The code runs fine up until the point that it tries to train a 16x submodel. Then I get the following error:

training submodel: 16x
Undefined variable "dagnn" or class "dagnn.Neg".

Error in LRRAddMasking (line 21)
net.addLayer(['neg_prob_' pre_up_name], dagnn.Neg(),
['prob_' pre_up_name], ['neg_prob_' pre_up_name], {});

Error in LRR4xTrainVGG16Pascal (line 254)
net = LRRAddMasking(net, upsample_fac(step),
upsample_fac(step)/opts.rec_upsample,
upsample_2x_pre_layer);

I've looked and the dagnn variable is undefined. Is this a known bug, or is it potentially linked to my MatConvNet setup (I have the latest version of that).

I'm running the code on a TitanX GPU. Any help is appreciated.

@golnazghiasi
Copy link
Owner

Hi,
Does it help to change "dagnn.Neg()" to "Neg()"?

@JoelChev
Copy link
Author

I will try that next. Right now I'm trying to add the Neg and DotProduct scripts directly into the +dagnn folder of /matconvnet/matlab to see if that fixes it.

@golnazghiasi
Copy link
Owner

I think I had them in my +dagnn folder of /matconvnet/matlab/ and because of that, I have "dagnn.Neg()" and "dagnn. DotProduct()" in my code. But, with the current set up that these methods are in modelInitialization folder "Neg()" and "DotProduct()" seem to be correct.

@JoelChev
Copy link
Author

Alright, thank you very much for clarifying so quickly! I think both approaches solve the problem. Might be worth pushing a fix so that others aren't caught in this bug though.

@golnazghiasi
Copy link
Owner

Great. I'll push a fix for this issue. Thanks for letting me know about it.

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