🦆N7PI PARC SedgwickRepeater
How this repeater scores
CoreScope · relative to this mesh- Bridgeweight 0.300.36 × 0.30 = 0.109
How much of the mesh has to pass through it. A chokepoint between two halves of a network scores high.
- Coverageweight 0.250.80 × 0.25 = 0.200
How much of the mesh it can reach, weighted so near neighbours count more than distant ones.
- Redundancyweight 0.250.00 × 0.25 = 0.000
What breaks if it vanishes. High means nothing else covers its job. Something else already covers what it does, so losing it would not split the mesh.
- Trafficweight 0.200.09 × 0.20 = 0.018
How much it actually relayed, measured rather than inferred from the map. It is carrying little traffic compared with the busiest repeater here.
What would actually change this
- About typical for the area
Coverage of 0.80 against an average of 0.67 across 8 repeaters within 25 miles.
- Redundancy at zero is good news
It means something else already covers this node’s job, so losing it would not split the mesh. Raising this number would mean making the network more fragile. It is the one figure here nobody should chase.
- Reachable, but not on anyone's path
It can hear plenty and is relaying little, which usually means traffic has shorter routes. That follows from where the people are, and tends to change on its own as the mesh grows.
Every axis is scored against the other repeaters this analyzer can see, so 1.00 means “the best of these” rather than perfect, and a grade here is not comparable with one from another mesh. CoreScope’s own note on the bands is that they are a first cut, not tuned against real data — so treat the letter as a rough impression and the number as the real answer.