|
Some checks failed
CI / changes (push) Successful in 7s
CI / changes (pull_request) Successful in 11s
CI / frontend-tests (push) Has been skipped
CI / openapi-codegen-check (push) Has been skipped
CI / backend-tests (push) Has been skipped
CI / frontend-tests (pull_request) Has been skipped
CI / openapi-codegen-check (pull_request) Successful in 1m40s
CI / backend-tests (pull_request) Failing after 8m48s
_GEO_WEIGHT_UNKNOWN was 0.1, which equals exp(−6.9/3)≈0.10 (weight of a confirmed-far project at ~6.9 km). Projects beyond that distance got a weight *below* 0.1, meaning unknown-coordinate projects outweighed confirmed-far ones — an inversion of the documented intent. Lowered to 0.05 (≈ exp(−3) = exp(−9 km / scale)), restoring the correct hierarchy: confirmed-close > confirmed-far > unknown. Updated TestGeoWeight (hardcoded 0.1 expectation) and TestCannibalizationTrueMode (overlap × floor comment/value) accordingly. Added two new assertions in TestGeoWeight that enforce the hierarchy monotonically and verify unknown < exp(−6.9/3). |
||
|---|---|---|
| .. | ||
| alembic | ||
| app | ||
| db/init | ||
| output | ||
| scripts | ||
| tests | ||
| .dockerignore | ||
| .env.example | ||
| .env.runtime.example | ||
| alembic.ini | ||
| debug.log | ||
| Dockerfile | ||
| pyproject.toml | ||
| uv.lock | ||