verne.freenode.net changed the topic of #mlpack to: http://www.mlpack.org/ -- We don't respond instantly... but we will respond. Give it a few minutes. Or hours. -- Channel logs: http://www.mlpack.org/irc/
tham has joined #mlpack
< tham>
I have a quick question about the test cases of convolution neural network
< tham>
Is it possible to add the prediction as part of the unit test?This way the users could learn how to predict and test the results of prediction at the same time
tham has quit [Ping timeout: 246 seconds]
tham has joined #mlpack
< tham>
I just study the source codes, looks like the ValidationError do not return the %
< rcurtin>
lotas: hi there, consider using the newest version of mlpack instead of mlpack 1.0.12 (or whatever other release)
< rcurtin>
in the latest git revision, the dependency on libxml2 is dropped in favor of boost serialization, so I think that will fix your issues
< rcurtin>
alternately, I suspect setting your include directories to '/usr/include/mlpack/;/usr/include/libxml2/' might solve your issue with netbeans
< rcurtin>
the libxml2 include directories were always a source of pain... on some distributions parser.h was in /usr/include/libxml/, on others, /usr/include/libxml/libxml2/... happy to not be depending on that anymore
< rcurtin>
I'm not sure which example you're referring to about the parsing, though, so I don't know if I can be helpful there without more information
< rcurtin>
I'll be online tomorrow from about 0830 UTC to 1730 UTC (long plane flight...) so maybe I can help with issues then, if you're around
< rcurtin>
tham: I think you read the IRC logs too; I'll spend some more time reading what you wrote tomorrow... need to get some sleep first :)
witness_ has quit [Quit: Connection closed for inactivity]
< zoq>
tham: I tested the code, but my results are completely okay even with 5 epochs instead of 50 (predict accuracy of 5 : 0.972, predict accuracy of 8 : 0.976).
< zoq>
tham: I guess the problem you run into are 'bad' initial weights. You can try another weight init rule or change some parameters of the current method, e.g., you could try the OrthogonalInitialization method. Another problem could be overfitting, you could track the prediction accuracy over time.