-
Notifications
You must be signed in to change notification settings - Fork 3
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
Inconsistency in ROIs returned #57
Comments
Thanks, Marta. What is INP?
If you try the neuprint_datasets() it shows two levels of neuropils. Could that be related? Best, Greg.
…Sent from my iPhone
On 28 Jan 2020, at 17:32, Marta Costa ***@***.***> wrote:
There are inconsistencies on which ROIs are returned, depending on what function is used.
In this case the INP mesh can't be retrieved, but it shows as an ROI when using neuprint_connection_table().
This might reflect issues in neuprint itself, so not sure if it can be fixed.
neuprint_ROI_mesh("INP")
Error: neuPrint error: Key "INP" not found
But
DM1.opn.connected = neuprint_connection_table(DM1.opn.info$bodyid, prepost = "POST")
table(DM1.opn.connected$roi)
AL(R) CA(R) INP LH(R) mALT(R) MB(+ACA)(R) MB(R) None
1064 1613 1 1659 45 1613 1613 128
SCL(R) SLP(R) SNP(R)
1 21 21
Examples from vignette https://github.com/natverse/neuprintr/blob/master/vignettes/hemibrain_opns.Rmd
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
INP does not show up in the ROI menu for meshes in neuprint explorer either. In general, we noticed that not all ROIs (depending on their position in the hierarchy) are available to all neuprint queries. This is for example true for the ROI connectivity. |
It’s inferior neuropils.
Brain regions list, top right here https://neuprint.janelia.org/
… On 28 Jan 2020, at 20:04, Romain Franconville ***@***.***> wrote:
INP does not show up in the ROI menu for meshes in neuprint explorer either.
In general, we noticed that not all ROIs (depending on their position in the hierarchy) are available to all neuprint queries. This is for example true for the ROI connectivity.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
This also affects connectivity numbers, since some ROIs seem to be overlapping and the connections are repeated with
|
@istvantaisz @mmc46 I have made changes to
|
@alexanderbates Thank you for fixing this problem. When I run your example 4, I get the following error message.
|
Related to the original bug https://twitter.com/stephenplaza/status/1222356894267953153?s=21 |
There are quite a few issues reported by FLYEM on number of synapses per neuropil, to be resolved in the next released version. https://docs.google.com/document/d/1vae3ClHR8z8uekqwrOHtqiux3oY5-Y_xw6W2srCi3PI/edit?usp=sharing |
Note that commit 95d12ba only fixed the issue reported by @tatsuookubo – the close by commit message feature is a bit more trigger happy than I realised so I have reopened. |
There are inconsistencies on which ROIs are returned, depending on what function is used.
In this case the INP mesh can't be retrieved, but it shows as an ROI when using
neuprint_connection_table()
.This might reflect issues in neuprint itself, so not sure if it can be fixed.
But
In this case, the synapses are attributed to INP (the higher level neuropil) and do not appear assigned to any of its lower level neuropils.
Examples from vignette https://github.com/natverse/neuprintr/blob/master/vignettes/hemibrain_opns.Rmd
The text was updated successfully, but these errors were encountered: