Skip to content
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

Conversion to dotprops for nblast(neuron, dotprops) [or vice versa] is rather inefficient #25

Open
jdmanton opened this issue Oct 2, 2014 · 2 comments
Assignees

Comments

@jdmanton
Copy link
Collaborator

jdmanton commented Oct 2, 2014

As the conversion happens in WeightedNNBasedLinesetMatching(), this means that the objects are converted for every comparison, not just once at the start, making everything much slower than it needs to be.

@jefferis
Copy link
Contributor

jefferis commented Oct 2, 2014

There is a difference between the conversion in WeightedNNBasedLinesetMatching and converting using e.g. dotprops(,resample=T). In the first case the direction vector is the vector from each point to its head point, without resampling. In the second case it is based on k nearest neighbours. It would probably be best to stick to pre-conversion to dotprops in most cases. I haven't profiled in ages, but I am not sure that the conversion part of WeightedNNBasedLinesetMatching.neuron is that slow since there is no nearest neighbour calculation or eigenvector decomposition.

@jdmanton
Copy link
Collaborator Author

jdmanton commented Oct 2, 2014

I meant the conversion I added in d55c544 to allow it to handle the situation where query and target are not of the same class. I tried doing this higher up, in nblast(), but this messed a few things up — it looks like it is worth me retrying this and attempting to fix the problems.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants