1.4.0

Performance release. Half the pops to simulate, at the same population.

The simulation iterates pops, not people, so the number that matters is people per pop. Across the 50 US LODES maps in the registry the median is 13.8 and Tampa is 26.5. This map was at 8.8 — below the 25th percentile.

	pops	people/pop
1.3.1	66,179	8.8
1.4.0	32,927	17.7
US LODES median (n=50)	—	13.8
Tampa	60,755	26.5

The base LODES layer was the whole of it — 5.1 people per pop, against 19.3 for the special demand. Two settings at the generator, both matching Tampa's config:

• DISTANCE_THRESHOLD_NONCBD 0.1 → 0.2, which on its own took the base from 53,586 pops to 21,805 for identical people
• CONSOLIDATE_POPS on, merging the small ones

The finer CBD threshold still applies downtown, so the peninsula keeps its resolution — the coarsening is only outside the central business district.

On top of that, identical commutes are now merged after the special demand is placed: the school and lodging allocators hand one residence node several pops bound for the same school or hotel, and those are one commute, not several. Anything above a 200-person trainload is split back out.

School pop size deliberately stays at 15 rather than rising to reach Tampa's ratio. Raising it to 25 would save another ~4,000 pops but drops the residential nodes eligible for a school seat from 1,470 to 1,231, which erodes the attendance-zone model for less than it gains.

Demand is unchanged in substance: 583,085 people across 2,566 points, median commute 20.8 km. Map files unchanged from 1.2.0.

Together with 1.3.1, demand_data.json has gone from 74 MB to 5.7 MB and the simulated entity count has halved.