ChanServ changed the topic of #mlpack to: Due to ongoing spam on freenode, we've muted unregistered users. See http://www.mlpack.org/ircspam.txt for more information, or also you could join #mlpack-temp and chat there.
SanguineAnomaly1 has joined #mlpack
SanguineAnomaly1 has quit [Remote host closed the connection]
ricklly has joined #mlpack
< ricklly>
hello, anyone can tell how to output "Log::Debug"
< ricklly>
I have touched the "-D DEBUG=ON" label to the cmake
witness has quit [Quit: Connection closed for inactivity]
< zoq>
ricklly: Hello, inside the test cases?
< zoq>
ricklly: Set mlpack::Log::Debug.ignoreInput = false; once before you ran the the code
< ShikharJ>
zoq: I made some suggestions to the Layer Serialization PR, do you hthink they're viable?
vivekp has joined #mlpack
< zoq>
ShikharJ: Haven't had the chance to take a look at the comments; it's on my list for the day
< ricklly>
ok, l try it immediately
< ricklly>
zoq: maybe I did not express my question. I mean I want the code "Log::Debug << debug info << endl;" output to termination, how to make it?
< zoq>
ricklly: So basically exit(0) after the output?
< ricklly>
no no no
< zoq>
hm, I guess I don't get the idea
< ShikharJ>
ricklly: Do you want all the information that is getting stored in Log::Debug to be output to the terminal?
< ShikharJ>
Is that what you're meaning to say?
< ricklly>
yeah
< ShikharJ>
zoq: Is there a straight-forward way to do that? I have only (in my previous work) directly changed Log::Info to std::cout but that's not something that ricklly would want to do.
< ShikharJ>
ricklly: Can you try the above and let us know if it helps your case?
htols1 has quit [Ping timeout: 246 seconds]
< ricklly>
now i am debugging an optimizer. there are some "Log::Debug << debug info" in the code. I want to them output to termination, but I tried and failed
< ShikharJ>
ricklly: In that case, I think the brute force std::cout in place of Log::Debug should work as well. Doesn't help you much in terms of convenience though.
< ShikharJ>
Sorry for that, I wish I had a better idea.
< ShikharJ>
rcurtin: Can you think of a way?
< ricklly>
ok, thanks
< rcurtin>
if this is in a test case there is also the TEST_VERBOSE CMake configuration option
< rcurtin>
it shouldn't be hard to get Log::Debug output but I'd need to know a little more about the code that is being tried
LarrySteeze1 has joined #mlpack
LarrySteeze1 has quit [Remote host closed the connection]