-
Notifications
You must be signed in to change notification settings - Fork 1
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
Type summary function #67
Comments
This problem looked similar to the "where to cut" problem in hierarchical clustering. Our query results generate a sub-taxonomy. If we think top-down, we should stop at some point which is not too specific (over-fitting) and not too generic. |
Agree this is underspecified so we just need to play. Is it a potential problem for the dendrogram-based approaches that our class hierarchy is be multi-inheritance? |
Yes, I was thinking the same issue. Alternatively, we can represent our multi-inheritence taxonomy with an adjacency matrix and apply a graph clustering approach (like spectral clustering). |
Spectral clustering didn't provided the expected abstraction points. I used three metrics:
After the get_connected_neurons_by_type query, tree construction and metrics evaluation adds 4.5 seconds execution time. |
Aim: Given a list of Individuals or Classes, provide a summary of the classes present
example
Histogram of types returned includes leaf nodes and subsuming classes, e.g. LC4, 14, 9 and 10 are subsumed by 'lobular columnar neuron'
In this case, all cells are subclasses of 'visual projection neuron' - so mapping up to that class would tell us nothing - but mapping up to a class below 'adult visual projection neuron' would be useful:
The problem, of course, is how we specify what classes we should map up to? We could allow user input of such classes, but I think that would be asking too much of our users. Is there an algorithm we can apply which selects some informative/representative set of subsuming classes to map up to? Maybe something that could take some tuning variable specifying degree of abstraction?
The text was updated successfully, but these errors were encountered: