print thicket tree by node order (hatchet nid) instead of alphabetically #174
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
dyokelson
added
area-visualization
dyokelson
added
type-bug
michaelmckinsey1
requested changes
Jun 13, 2024
Co-authored-by: Michael McKinsey <MichaelMcKinsey1@gmail.com>
pearce8
approved these changes
Jun 13, 2024
michaelmckinsey1
approved these changes
Jun 13, 2024
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 changes the printing of the thicket tree from alphabetical (frame) to node order (_hatchet_nid). If the profile does not have node ordering (from old caliper, or some other format) it will still sort the print by _hatchet_nid, which can be assigned alphabetically, possibly resulting in alphabetical printing of the thicket tree.