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/
sgupta1 has joined #mlpack
sgupta has quit [Write error: Connection reset by peer]
< rcurtin>
sgupta: that seems like a little bit of a hack, I think instead you should investigate why boost isntalled with such weird permissions
kris1 has quit [Quit: kris1]
sgupta has quit [Ping timeout: 255 seconds]
sgupta has joined #mlpack
kris1 has joined #mlpack
kris1 has quit [Quit: kris1]
< rcurtin>
lozhnikov: any chance you can send a link to the DVK-3M you found for sale for $250? I think I would like to use that data point as bargaining fodder :)
< rcurtin>
I did a quick calculation, if all the remaining benchmark jobs for shogun time out at 9000 seconds, assuming each only runs once, then the shogun benchmark will finish in about 5.5 days...
< zoq>
hm, I guess if they time out anyway, there is no good reason to wait
< zoq>
I guess, it makes sense to look into the issue and restart the benchmark later
< rcurtin>
would you like to do that? I'm happy to wait a few more days
< rcurtin>
but definitely if we wanted to kill it and look into the failures that is ok too
< rcurtin>
there's no guarantee that the remaining jobs will fail---my estimation was only a worst-case guess (and it's only right if each method runs only once, which I think is the case)
vivekp has quit [Ping timeout: 255 seconds]
< zoq>
Not sure I have the time to look into the issue today or tomorrow, so I don't mind to wait. On the other side if someone has time to look into it, I think there is no good reason to wait.
< zoq>
I know, you are waiting for a restart.
sgupta1 has joined #mlpack
sgupta has quit [Ping timeout: 240 seconds]
< rcurtin>
yeah, but no hurry on that
< rcurtin>
5.5 days is fine with me, if it was a month I would do something about it :)