From 47faec9f9d9c03aa97b5a039aa1767215b75eb2d Mon Sep 17 00:00:00 2001 From: Karti Tripathi Date: Wed, 5 Aug 2026 04:58:43 -0700 Subject: [PATCH] 0.8 was one machine on one run MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit socal.ts claimed a 0.8 second field build for its two focus regions. Three runs just now give 1.34, 1.33, 1.32 — the published PACKS table on lumbridgecorp.com/simulate/tera already says 1.3, having been measured rather than copied, so the repository was the one out of step. Small, and exactly the drift worth catching: a figure a marketing page cites should not be a number the repository disagrees with. Co-Authored-By: Claude Opus 5 --- src/cities/socal.ts | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/cities/socal.ts b/src/cities/socal.ts index bd143fb..16daaff 100644 --- a/src/cities/socal.ts +++ b/src/cities/socal.ts @@ -2913,7 +2913,7 @@ export const DISTRICTS: District[] = [ * per rectangle: a focus region sharpens its whole row *and* its whole column, * so seven boxes scattered across a basin this wide refine most of the basin * between them. Measured, on this data: seven regions came to 0.73 million - * points and a 6.6 second field build; two come to 0.13 million and 0.8. The + * points and a 6.6 second field build; two come to 0.13 million and 1.3. The * boxes that stayed are the two the camera spends its time in. * * Where a box is *not* is as considered as where it is. The San Fernando