examples: centrality distribution, max-norm vs percentile - #170
Open
Anandb71 wants to merge 1 commit into
Open
Conversation
Adds the measurement tool used to recalibrate the v2.6.0 risk thresholds. For any indexed directory it prints what fraction of nodes sit above a given centrality under both the old max-normalised scale and the percentile rank that replaced it, then reports which percentile selects the same population the old bars did. That comparison is why the thresholds moved. Max-normalisation divides by the single most central node, so one numeric cutoff selects wildly different fractions depending on how peaked a repository's graph happens to be. Percentile rank does not — but the old cutoffs had been tuned against the old scale, and carrying them across unchanged silently redefined what "high risk" meant. Usage: cargo run -p arbor-watcher --example centrality_dist -- <dir>
🟡 Arbor PR WalkThe file centrality_dist.rs has 1 symbol changed. It has no direct callers. This change reaches 8 downstream points.
Changed Files
✅ Before You Merge
📊 Analysis confidence: High · 1275 nodes · 8588ms
Arbor · View full report → · arbor v2.6.0 · 8588ms · 1275 nodes · verify locally with |
🌳 Arbor Impact ReportRisk Level: 🟢 Low | Blast Radius: 8 nodes | Changed Symbols: 1 Changed Files
📊 Visual Impact Graphgraph TD
classDef changed fill:#ef4444,stroke:#333,stroke-width:2px,color:#fff;
classDef caller fill:#f59e0b,stroke:#333,stroke-width:1px,color:#fff;
class main changed;
Impact Summary
Powered by Arbor v2.6.0 — graph-native code intelligence |
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
1 participant
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.
Adds the measurement tool used to recalibrate the v2.6.0 risk thresholds.
For any indexed directory it prints what fraction of nodes sit above a given centrality under both the old max-normalised scale and the percentile rank that replaced it, then reports which percentile selects the same population the old bars did.
That comparison is why the thresholds moved. Max-normalisation divides by the single most central node, so one numeric cutoff selects wildly different fractions depending on how peaked a repository's graph happens to be. Percentile rank does not — but the old cutoffs had been tuned against the old scale, and carrying them across unchanged silently redefined what "high risk" meant.
Examples only. No production code touched.