Node importance - #57
Open
traines-source wants to merge 14 commits into
Open
Conversation
mority
approved these changes
Aug 29, 2025
traines-source
force-pushed
the
importance
branch
from
August 29, 2025 15:08
2f5d2de to
d17d7eb
Compare
This reverts commit 7640a49.
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Node importance can be accessed with:
r_->node_importance_[node_idx]toggle between OSM-based importance heuristic and InertialFlowCut with
USE_INERTIAL_FLOW_CUTin ways.cc:11OSM-based importance: 0 is low importance, 7 is high importance
IFC: 0 is low "importance",
n_nodes()-1is high "importance"