Add a UUID to each PathObject #959
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This is a fairly major change to incorporate IDs for objects. The purpose is to make it much easier to match up objects whenever some further analysis is done elsewhere (e.g. classification or clustering in Python). I've attempted to ensure both forwards and backwards compatibility by storing the ID in the metadata map. This is somewhat inefficient, but means that data files can be reopened in earlier QuPath versions. A future QuPath release might change this to a more efficient representation.
Now it is more like Thread.currentThread().getId()
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a fairly major change to incorporate IDs for objects.
The purpose is to make it much easier to match up objects whenever some further analysis is done elsewhere (e.g. classification or clustering in Python).
I've attempted to ensure both forwards and backwards compatibility by storing the ID in the metadata map. This is somewhat inefficient, but means that data files can be reopened in earlier QuPath versions. A future QuPath release might change this to a more efficient representation.