07:58 < ranjan123> rcurtin: you there ?

14:09 < uzipaz> any mentors around right now?

14:10 < uzipaz> FeedForwardNetworkTest is failing, im getting unknown_location fatal error on loading thyroid_train.csv

14:12 < uzipaz> All tests programs that load dataset into memory are failing due to not being able to read the datasets

14:22 < ranjan123> I think all the montors are tired of replying ! I haven't got any reply from last 3 days. :P

14:29 < uzipaz> that is sad, I wanted to use the library on a dataset but I just wanted to make sure the library is installed and configured properly, the tests are failing on a seemingly trivial problem, I've been trying to fix this for days to no avail

14:36 < ranjan123> hmmm

14:37 < ranjan123> bw . where r you from ?

14:37 < ranjan123> *btw

14:43 < wasiq> Its probably easter where they live and they need a break so give them time.They WILL reply eventually.

14:49 < ranjan123> hmm. :D

14:49 < ranjan123> hi wasiq

14:51 < ranjan123> let us talk something different from gsoc

14:51 < ranjan123> :S

14:54 < ranjan123> I guess nobody has time for that .. :(

16:10 < zoq> wasiq: Hello, I guess if you use the build directory as root directory it should work: bin/mlpack_test -t FeedForwardNetworkTest instead of mlpack_test -t FeedForwardNetworkTest

16:15 < wasiq> ranjan123, Sure.But by unsaid IRC rules you cant expect an immediate reply. You should be looking at facebook or omegle for long deep conversations.

16:18 < zoq> wasiq: Let me now if this helps.

16:18 < zoq> wasiq: ah wrong username, sorray

16:35 < ranjan123> got it! zoq . :-|

16:43 < ranjan123> sorry for talking about some irrelevant things. I was not aware of that rules.

16:43 < ranjan123> :)

16:47 < wasiq> zoq, yup uzipaz left. He might come back later.

16:48 < wasiq> ranjan123, Its alright :)

17:12 < rcurtin> ranjan123: wasiq: you guys are free to talk about whatever, it's okay :)

17:13 < rcurtin> I am on vacation this week so I haven't been able to reply much

17:23 < wasiq> ranjan123, then i have no issues with talking :) but i might not reply immediately sometimes.

17:24 < uzipaz> Hello zoq, I am running the tests now and they work... it outputs only 'no errors detected'... just wanted to confirm that is it because I compiled with no debugging and profile?

17:31 < zoq> uzipaz: Sounds great, you can complile with "cmake -D TEST_VERBOSE=ON" but unless you don't use Log::Debug anywhere you shouldn't get any results when running the tests.

17:47 < uzipaz> zoq: since I have the library compiled with -DDEBUG=OFF, -DPROFILE=OFF, if I am writing code using the library and I make some compile time/runtime errors, I will not get feedback from the compiler/program?

17:50 < uzipaz> zoq: but anyway, thanks for answering my questions...

17:53 < zoq> uzipaz: You get compile time/runtime errors even if you turn debug and profile off. If you build mlpack with DEBUG=ON you compile with debugging symbols and without any compiler optimization and if you build with PROFILE you get profiling symbols. If you don't use a debugger you should be fine.

18:58 < ranjan123> zoq:

18:58 < ranjan123> what is the use of Log::Info

18:58 < ranjan123> ?

18:59 < ranjan123> How can see those msg with Log::Info ?

18:59 < ranjan123> How can I see those msg with Log::Info ?

19:00 < rcurtin> ranjan123: pass the --verbose option if it is a command-line program

19:00 < rcurtin> (or -v)

19:01 < ranjan123> do you mean this --> ./bin/mlpack_test -v -t SGDTest

19:05 < rcurtin> oh, you are using the test... then run CMake with -DTEST_VERBOSE=ON

19:05 < ranjan123> I dont see any --verbose option here -> ./bin/mlpack_test --help

19:05 < ranjan123> ohh

19:05 < rcurtin> you're right, the mlpack_test program doesn't use the same command-line parsing as the command-line mlpack programs

19:05 < rcurtin> sorry for the confusion

19:05 < ranjan123> Yes I did!

19:05 < rcurtin> the tutorials should be updated to point out that the TEST_VERBOSE option exists

19:05 < rcurtin> okay, and you are getting no [INFO ] output when you run the tests?

19:06 < ranjan123> yes ! I am not getting any msg for Log::Info

19:06 < rcurtin> okay

19:06 < rcurtin> are the tests you are running outputting anything to Log::Info?

19:07 < ranjan123> yes ! I am expected to get the msg

19:07 < rcurtin> when you re-ran cmake, did you recompile the entire program?

19:08 < rcurtin> I don't have time to debug your issue here

19:08 < rcurtin> I am about to leave (like I said I am on vacation)

19:08 < ranjan123> ok ok ! let me check again .

19:08 < ranjan123> :)

19:08 < rcurtin> try removing your build directory and recompiling... without digging deeper there is nothing I can suggest

19:08 < ranjan123> hmmm

19:08 < ranjan123> Thanks

19:27 < zoq> ranjan123: Even if you build with TEST_VERBOSE=ON; you get only the Log::Debug output.

19:27 < zoq> ranjan123: I'm not sure why you like to get the output from Log::Info when running a test, however, you could set 'mlpack::Log::Info.ignoreInput = false;' inside the test case, to get the output from Log::Info and 'mlpack::Log::Warn.ignoreInput = false;' to get the output from Log::Warn.

19:35 < ranjan123> zoq: Now It is working, after using mlpack::Log::Info.ignoreInput = false

19:36 < ranjan123> zoq: I Like to get those output for debuging purpose.

19:37 < ranjan123> thanks!

19:37 < zoq> ranjan123: ah okay, but you could also use Log::Debug << "message" << std::endl;

19:38 < ranjan123> Then I have to compile it with -DDEBUG=ON

19:38 < ranjan123> right ?

19:39 < ranjan123> which will take lot of time

19:39 < ranjan123> I guess

19:42 < zoq> hm, I'm not sure it takes longer to build, but the test probably takes way more time in DEBUG mode.

19:42 < rcurtin> ranjan123: sorry, I guess I misunderstood what TEST_VERBOSE did

19:46 < ranjan123> zoq: hmmm.

19:46 < ranjan123> rcurtin: Now it ok. :)

19:46 < ranjan123> *is