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

FlyEM male OpticLobe synapse information #174

Open
emilkind opened this issue May 31, 2024 · 2 comments
Open

FlyEM male OpticLobe synapse information #174

emilkind opened this issue May 31, 2024 · 2 comments

Comments

@emilkind
Copy link

When querying synapses from the new FlyEM OpticLobe data with neuprint_get_synapses() it would be really helpful if the layer and column information for each synapse would also be returned.

cypher query could look something like this:

"MATCH (a:Neuron)-[:Contains]->(:SynapseSet)-[:Contains]->(s:Synapse)-[:SynapsesTo]->(:Synapse)<-[:Contains]-(:SynapseSet)<-[:Contains]-(b:Neuron) WHERE a.bodyId IN %s RETURN a.bodyId AS body_id, a.instance AS instance, a.type AS type, s.type AS prepost, s.confidence AS confidence, s.olLayer AS optic_lobe_layer, s.roi AS ROI, s.olHex1 AS hex1, s.olHex2 AS hex2, b.bodyId AS partner_body_id, b.instance AS partner_instance, b.type AS partner_type"

@jefferis
Copy link
Contributor

Thanks for the suggestion. I'm afraid that requires some dataset specific logic and neuprintr should be generic. Perhaps the neuprintr function could provide an argument to specify extra fields? Additional suggestions or PRs welcome!

@emilkind
Copy link
Author

True. Maybe a details argument similar to flywire_partners() from the fafbseg package which would return more info in a dataset specific fashion.

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

2 participants