-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
RANN.L1 remote dependency #31
Comments
tl;dr
Thanks! |
@krlmlr you had a strategy for this I think? |
In #30, I suggested to re-unify the codebases so that L1 is available from {RANN}. Would that work? |
If the master branch of a new repo at |
Can we give @krlmlr the option to try and get things working in one package. Having two repos would be a retrograde step when we are trying to rationalise two separate packages. |
Sounds like an optimal solution, thanks! |
@combiz: For me, |
|
Hi friends... thank you for you RANN (and RANN.L1)! I'm curious about use of Lp for p = [ .... drum roll .... ] 1/2. It looks possible to hotwire the RANN tarball library by commenting out / uncommenting in at that spot in ANN.h and running R CMD SHLIB ... but that would be a first for me, and I ran across this thread and thought I'd ask if "rationalising" (as @jefferis put it) RANN to run ANN with different p value options was in the cards. Thanks again for your contributions! Cheers! |
See the ANN manual for metrics that are supported out of the box. Not including 1/2 https://www.cs.umd.edu/~mount/ANN/Files/1.1.2/ANNmanual_1.1.pdf |
Right. Yes, I'd seen this ... there's no triangle inequality and hence no "metric" with 0 < p < 1 but the quantities from these "fractional" p distances can still be used to define neighborhoods around query points for ANN search. There's some literature on such fractional distances helping with the curse of dimensionality story in the 20-50 dimension range, hence my curiosity. Cheers! |
I'm creating a package which requires "RANN.L1" as a dependency. The package "RANN.L1" is therefore listed under
Imports:
in theDESCRIPTION
file of the package, and the remote dependency location is specified asjefferis/RANN@master-L1
underRemotes:
in the same file. However, as RANN.L1 is a branch of the RANN repo, the package build under Travis CI fails, presumably as it can't associate the "RANN.L1" import with the "RANN" remote. Any suggestions? Having thejefferis/RANN@master-L1
branch as a separate repo underjefferis/RANN.L1
could be a quick fix? Thanks.The text was updated successfully, but these errors were encountered: