Closed vigsterkr closed 11 years ago
I think they just take too long... - this cell ran for ~50mins cpu time before the timeout killed it
maybe you just take a subset or converge early or can you speed it up further ?
I will have a look at it during the weekend. I think I will probably go for using less dimensions.
currently only one is failing
running /home/buildslave/nightly_default/build/doc/ipython-notebooks/metric/LMNN.ipynb
Failed to run cell:
from modshogun import LMNN
# number of targer neighbours in LMNN, here we just use the same value that was used for KNN before
k = 3
lmnn = LMNN(ape_features, ape_labels, k)
lmnn.set_diagonal(True)
lmnn.set_maxiter(1200)
init_transform = numpy.eye(ape_features.get_num_features())
lmnn.train(init_transform)
diagonal = numpy.diag(lmnn.get_linear_transform())
print('%d out of %d elements are non-zero.' % (numpy.sum(diagonal != 0), diagonal.size))
1 cells failed to complete
25 code cells from notebook
it is too slow anyways - slower than FGM (eating > 90mins of CPU before being killed)
90 mins??? the last time it was running successfully was 25m1.033s
Look closely:
http://buildbot.shogun-toolbox.org/builders/nightly_default/builds/554/steps/notebooks/logs/stdio
123mins CPU time!
All right, I am updating it to use less number of features right away. On 29 Sep 2013 22:31, "Soeren Sonnenburg" notifications@github.com wrote:
Look closely:
http://buildbot.shogun-toolbox.org/builders/nightly_default/builds/554/steps/notebooks/logs/stdio
123mins CPU time!
— Reply to this email directly or view it on GitHubhttps://github.com/shogun-toolbox/shogun/issues/1687#issuecomment-25328529 .
Updated in #1698
@sonney2k, shall we rebuild and see if it behaves better now? This time took about 15 seconds in my computer.
@iglesias it took 2m16s now so it is OK.
@sonney2k great to know, thanks!
any ideas?