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

Unexpected behavior when working with classifications with > 2 levels #39

Closed
petebankhead opened this issue Jan 8, 2017 · 1 comment
Labels
bug v0.1.2 Issue affecting v0.1.2 (or earlier)

Comments

@petebankhead
Copy link
Member

Object classifications can form hierarchies in QuPath, as described in the documentation.

A derived class should be shown with a colon separator, e.g. Tumor: Positive and Tumor: Negative are both derived from a base classification of Tumor.

This appears to work fine, but if there are more than two 'levels' to the classification then only the final two are displayed through the user interface. Therefore while Tumor: E-cadherin: Positive can be represented in code, it would only be shown as E-cadherin: Positive on screen.

The following script can be used to print out what all the levels of the classification are.

// Get classification of selected object
def pathClass = getSelectedObject().getPathClass()
println("Classification is " + pathClass)
if (pathClass == null) {
    return
}

// Print the full classification
String fullName = pathClass.getName()
pathClass = pathClass.getParentClass()
while (pathClass != null) {
    fullName = pathClass.getName() + ": " + fullName
    pathClass = pathClass.getParentClass()
}
println("Full classification hierarchy is " + fullName)

Additionally, the Classify by specific feature command does not pay much attention to hierarchies of classification - which is somewhat unintuitive, and requires updating (or replacing).

@petebankhead petebankhead added the v0.1.2 Issue affecting v0.1.2 (or earlier) label Aug 5, 2019
petebankhead added a commit that referenced this issue Feb 14, 2020
Implemented entry search in projects
@petebankhead
Copy link
Member Author

Fixed in v0.2.0.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug v0.1.2 Issue affecting v0.1.2 (or earlier)
Projects
None yet
Development

No branches or pull requests

1 participant