BikeNetKit / BikeNetKit/LinkBikeNet
mismatch lcc/network length
- Dominant language
- Jupyter Notebook
- Stars
- 3
- Forks
- 0
- Avg merge
- 1m
- Merged PRs (30d)
- 9
Description
**Describe the bug**
Length of largest component and network does not match up 100% after end step. Could be due to rounding or length calculations
**Expected behavior**
After running the algorithm, the last edge that is added should lead to the largest component and the network having the same size, since there is only one component left.
**Desktop (please complete the following information):**
- OS: macOS
- Version: as of 10.08.2026
**You have a solution? (optional)**
Potentially rounding issues, look into precision/how length gets calculated on geometries/graph.
Contributor guide
Research direction
Run the algorithm through its final step and compare the largest-component and network lengths after the last edge is added. Inspect the length calculations on the geometries and graph, including precision and rounding. Done means the final largest component and network sizes match.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100