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

neuprint_common_connectivity broken #67

Open
romainFr opened this issue Feb 3, 2020 · 7 comments
Open

neuprint_common_connectivity broken #67

romainFr opened this issue Feb 3, 2020 · 7 comments
Assignees

Comments

@romainFr
Copy link
Collaborator

romainFr commented Feb 3, 2020

Fails with

Error in names(x) <- paste("V", seq_along(x), sep = "") : 
  'names' attribute [1] must be the same length as the vector [0]
@jefferis
Copy link
Contributor

jefferis commented Feb 3, 2020 via email

@jefferis
Copy link
Contributor

jefferis commented Feb 4, 2020

@romainFr is this related to change of dataset to hemibrain:v1.0.1?

@romainFr
Copy link
Collaborator Author

romainFr commented Feb 4, 2020

My mistake, it is actually working. I got confused because it only returns partners common to all inputed neurons and I was looking for partners common to some (at least two) of the inputed neurons.

@romainFr romainFr closed this as completed Feb 4, 2020
@mmc46
Copy link
Contributor

mmc46 commented Feb 4, 2020

Sorry to maybe reopen, but then this

it only returns partners common to all inputed neurons and I was looking for partners common to some (at least two) of the inputed neurons.

is different behaviour to neuPrint Explorer, where common partners to a subset of bodyids are returned.
Example bodyids: 1734350788,1734350908,1765040289,5813039315,722817260

Just wanted to double check it is correct.

@romainFr
Copy link
Collaborator Author

romainFr commented Feb 4, 2020

Actually for me now neuprint explorer returns all the partners of all the neurons (whether any of those partners are in common or not), which is not super useful. Maybe we could have an ALL/ANY option in neuprintr_common_connectivity to switch between different behaviors?

@romainFr romainFr reopened this Feb 4, 2020
@alexanderbates
Copy link
Collaborator

I don't really use this function very much, nor am I sure that others in our group do. So feel free to update it to work sensibly. The behaviour does not need to be the same a neuPrint explorer, if whatever we go with is more useful and well documented.

@jefferis
Copy link
Contributor

jefferis commented Feb 4, 2020

I also agree that requiring partners to have connections to all the query neurons is not the behaviour I would expect. However more importantly, the prepost argument again seems to be backwards. i.e. you specify pre and you get the outputs.

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

No branches or pull requests

4 participants