[mlpack-git] [mlpack/mlpack] Major changes to solve issue: #275. (#624)

Ryan Curtin notifications at github.com
Mon May 2 10:46:18 EDT 2016


Sorry for the slow response on this; it took me a little while to wrap my head around what is going on here.  If I am understanding right, your question boils down to this: when you reorder the dataset to create children, you lose knowledge of what the near set is.  To me it seems like unless you preserve the near set itself separately, or recalculate distances after children are created (which will be slow), you are right: there is no way to do that that I can think of.  So probably maintaining the indices in the near set in a separate vector is the way to do this, I think.

I hope I've understood your q

---
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/mlpack/mlpack/pull/624#issuecomment-216254993
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.cc.gatech.edu/pipermail/mlpack-git/attachments/20160502/a9237530/attachment.html>


More information about the mlpack-git mailing list