homemaker-py-9yx: health-centre — non-synthetic third example programme
A small primary-care health centre: 19 distinct, individually-sized room codes at n=20 room instances (only one deliberate duplication: two public WCs), filling the gap between programme-house's duplicated-count sweep sizes and harbor-house's out-of-range 37 real-diversity instances. Widths are deliberately tiered (>1.3x gaps at three boundaries) so the auto-derived interchange relation resolves to three bounded utility/office/clinical classes instead of one whole-building chain, which a first pass produced. experiments/run_9yx_sweep.sh repeats xyu's ruin_recreate ON/OFF protocol (budget 3000, 4 workers, N=15 seeds) against this programme.
This commit is contained in:
parent
e5fee7eddf
commit
ce3fed166f
4 changed files with 416 additions and 21 deletions
|
|
@ -58,7 +58,7 @@
|
||||||
{"id":"homemaker-py-nyb","title":"High-locality topology operators (mutation + subtree crossover)","description":"DESIGN.md §5, §7 Phase 2, §8.4. Mutation moves: divide/undivide leaf, swap children, rotate cut, retype leaf, per-floor delta edits, storey add/delete (cf. Urb Mutate.pm — but geometry sliding belongs to the inner loop, not the operator set). Crossover: area-matched subtree exchange (a subtree = a contiguous region, so crossover is meaningful — Crossover.pm). Operators must be high-locality: small genome change =\u003e small phenotype change, so warm-started inner loops stay cheap.","acceptance_criteria":"Each operator produces valid genomes (oracle scores them without error); locality measured (mean fitness/geometry perturbation per operator)","status":"closed","priority":2,"issue_type":"feature","assignee":"Bruno Postle","owner":"bruno@postle.net","created_at":"2026-06-11T23:37:27Z","created_by":"Bruno Postle","updated_at":"2026-06-12T13:07:37Z","started_at":"2026-06-12T12:54:23Z","closed_at":"2026-06-12T13:07:37Z","close_reason":"operators.py lands: 7 mutations + area-matched crossover, valid-by-construction via genome.encode repair. 115/115 oracle-valid children; locality measured: geom-pert 0.07-0.33 per op, fitness-pert 0.68-0.99 (0.5^n cliff flags raw moves — warm restart + penalty reshaping confirmed load-bearing). Also fixed dom._link stale below-links on structural mutation.","dependencies":[{"issue_id":"homemaker-py-nyb","depends_on_id":"homemaker-py-k2g","type":"blocks","created_at":"2026-06-12T00:39:36Z","created_by":"Bruno Postle","metadata":"{}"}],"dependency_count":1,"dependent_count":1,"comment_count":0}
|
{"id":"homemaker-py-nyb","title":"High-locality topology operators (mutation + subtree crossover)","description":"DESIGN.md §5, §7 Phase 2, §8.4. Mutation moves: divide/undivide leaf, swap children, rotate cut, retype leaf, per-floor delta edits, storey add/delete (cf. Urb Mutate.pm — but geometry sliding belongs to the inner loop, not the operator set). Crossover: area-matched subtree exchange (a subtree = a contiguous region, so crossover is meaningful — Crossover.pm). Operators must be high-locality: small genome change =\u003e small phenotype change, so warm-started inner loops stay cheap.","acceptance_criteria":"Each operator produces valid genomes (oracle scores them without error); locality measured (mean fitness/geometry perturbation per operator)","status":"closed","priority":2,"issue_type":"feature","assignee":"Bruno Postle","owner":"bruno@postle.net","created_at":"2026-06-11T23:37:27Z","created_by":"Bruno Postle","updated_at":"2026-06-12T13:07:37Z","started_at":"2026-06-12T12:54:23Z","closed_at":"2026-06-12T13:07:37Z","close_reason":"operators.py lands: 7 mutations + area-matched crossover, valid-by-construction via genome.encode repair. 115/115 oracle-valid children; locality measured: geom-pert 0.07-0.33 per op, fitness-pert 0.68-0.99 (0.5^n cliff flags raw moves — warm restart + penalty reshaping confirmed load-bearing). Also fixed dom._link stale below-links on structural mutation.","dependencies":[{"issue_id":"homemaker-py-nyb","depends_on_id":"homemaker-py-k2g","type":"blocks","created_at":"2026-06-12T00:39:36Z","created_by":"Bruno Postle","metadata":"{}"}],"dependency_count":1,"dependent_count":1,"comment_count":0}
|
||||||
{"id":"homemaker-py-k2g","title":"Topology genome: base-floor tree + per-floor deltas + type assignment","description":"DESIGN.md §5.2, §7 Phase 2. Genome = base-floor slicing topology (primary) + per-leaf type assignment + per-floor divide/undivide deltas (Below-inheritance as regulariser; cut owned by lowest storey where its path is divided — §10). Must round-trip to/from dom.py Node trees so the oracle and inner loop consume it directly. Includes storey count and per-floor type overrides.","acceptance_criteria":"Genome \u003c-\u003e .dom round-trip on all 35 corpus files preserves fitness; multi-storey wall stacking preserved","status":"closed","priority":2,"issue_type":"feature","assignee":"Bruno Postle","owner":"bruno@postle.net","created_at":"2026-06-11T23:37:26Z","created_by":"Bruno Postle","updated_at":"2026-06-12T12:52:34Z","started_at":"2026-06-12T10:55:21Z","closed_at":"2026-06-12T12:52:34Z","close_reason":"genome.py encode/decode lands. 35/35 oracle fitness parity after round-trip (flag-on); genome fixed-point + owned-projection tests. Dead-field discovery: corpus upper storeys carry drifted dead divisions (97) and rotations (187) — canonicalised by decode, validated fitness-neutral.","dependency_count":0,"dependent_count":1,"comment_count":0}
|
{"id":"homemaker-py-k2g","title":"Topology genome: base-floor tree + per-floor deltas + type assignment","description":"DESIGN.md §5.2, §7 Phase 2. Genome = base-floor slicing topology (primary) + per-leaf type assignment + per-floor divide/undivide deltas (Below-inheritance as regulariser; cut owned by lowest storey where its path is divided — §10). Must round-trip to/from dom.py Node trees so the oracle and inner loop consume it directly. Includes storey count and per-floor type overrides.","acceptance_criteria":"Genome \u003c-\u003e .dom round-trip on all 35 corpus files preserves fitness; multi-storey wall stacking preserved","status":"closed","priority":2,"issue_type":"feature","assignee":"Bruno Postle","owner":"bruno@postle.net","created_at":"2026-06-11T23:37:26Z","created_by":"Bruno Postle","updated_at":"2026-06-12T12:52:34Z","started_at":"2026-06-12T10:55:21Z","closed_at":"2026-06-12T12:52:34Z","close_reason":"genome.py encode/decode lands. 35/35 oracle fitness parity after round-trip (flag-on); genome fixed-point + owned-projection tests. Dead-field discovery: corpus upper storeys carry drifted dead divisions (97) and rotations (187) — canonicalised by decode, validated fitness-neutral.","dependency_count":0,"dependent_count":1,"comment_count":0}
|
||||||
{"id":"homemaker-py-d0s","title":"Experiment: inner-loop optimiser bake-off at equal oracle budgets","description":"DESIGN.md §7 Phase 1, §8.3. DOF is only ~rooms-1 (6–7 on corpus). Compare Nelder-Mead vs CMA-ES vs batched multi-start pattern search at equal oracle-call budgets, measuring fitness gained per oracle call and wall-clock (batch-friendliness matters — §4.6). Measure, don't commit blind.","acceptance_criteria":"Table of fitness-per-budget across \u003e=3 candidates; one optimiser chosen and recorded in DESIGN.md","status":"closed","priority":2,"issue_type":"task","assignee":"Bruno Postle","owner":"bruno@postle.net","created_at":"2026-06-11T23:36:59Z","created_by":"Bruno Postle","updated_at":"2026-06-13T08:48:13Z","started_at":"2026-06-12T21:22:15Z","closed_at":"2026-06-13T08:48:13Z","close_reason":"Bake-off complete: CMA-ES confirmed as Phase 1/2 optimiser. NM wins quality per eval but sequential architecture incompatible with batching (§4.6). Compass stalls on narrow valleys. Results in DESIGN.md §8.3 and experiments/bakeoff_innerloop.*","dependencies":[{"issue_id":"homemaker-py-d0s","depends_on_id":"homemaker-py-1p0","type":"blocks","created_at":"2026-06-12T00:39:35Z","created_by":"Bruno Postle","metadata":"{}"}],"dependency_count":1,"dependent_count":0,"comment_count":0}
|
{"id":"homemaker-py-d0s","title":"Experiment: inner-loop optimiser bake-off at equal oracle budgets","description":"DESIGN.md §7 Phase 1, §8.3. DOF is only ~rooms-1 (6–7 on corpus). Compare Nelder-Mead vs CMA-ES vs batched multi-start pattern search at equal oracle-call budgets, measuring fitness gained per oracle call and wall-clock (batch-friendliness matters — §4.6). Measure, don't commit blind.","acceptance_criteria":"Table of fitness-per-budget across \u003e=3 candidates; one optimiser chosen and recorded in DESIGN.md","status":"closed","priority":2,"issue_type":"task","assignee":"Bruno Postle","owner":"bruno@postle.net","created_at":"2026-06-11T23:36:59Z","created_by":"Bruno Postle","updated_at":"2026-06-13T08:48:13Z","started_at":"2026-06-12T21:22:15Z","closed_at":"2026-06-13T08:48:13Z","close_reason":"Bake-off complete: CMA-ES confirmed as Phase 1/2 optimiser. NM wins quality per eval but sequential architecture incompatible with batching (§4.6). Compass stalls on narrow valleys. Results in DESIGN.md §8.3 and experiments/bakeoff_innerloop.*","dependencies":[{"issue_id":"homemaker-py-d0s","depends_on_id":"homemaker-py-1p0","type":"blocks","created_at":"2026-06-12T00:39:35Z","created_by":"Bruno Postle","metadata":"{}"}],"dependency_count":1,"dependent_count":0,"comment_count":0}
|
||||||
{"id":"homemaker-py-9yx","title":"Non-synthetic third example programme to isolate ruin_recreate room-count threshold","description":"y51/xyu follow-up (option b, not run by xyu). The synthetic n=10/14/18/22 sweep scales room count by duplicating already-interchangeable programme-house room codes (count: on b1/t1/b2/t2) -- the same mechanism harbor-house itself uses 'to reduce complexity'. xyu extended n=18 to N=15 seeds (DESIGN.md 31): trend weakened but did not evaporate (9.3%-\u003e6.4%, two-sided Wilcoxon p 0.098-\u003e0.059), still ambiguous. A genuinely distinct third example programme with real room-type diversity at an intermediate room count (not a duplicated-code scale-up) would avoid the interchangeable-room confound and better isolate room count as the driving variable behind the wing-rebuild-fraction hypothesis from f1d (DESIGN.md 23).","status":"open","priority":3,"issue_type":"task","owner":"bruno@postle.net","created_at":"2026-07-29T09:07:48Z","created_by":"Bruno Postle","updated_at":"2026-07-29T09:07:48Z","dependency_count":0,"dependent_count":0,"comment_count":0}
|
{"id":"homemaker-py-9yx","title":"Non-synthetic third example programme to isolate ruin_recreate room-count threshold","description":"y51/xyu follow-up (option b, not run by xyu). The synthetic n=10/14/18/22 sweep scales room count by duplicating already-interchangeable programme-house room codes (count: on b1/t1/b2/t2) -- the same mechanism harbor-house itself uses 'to reduce complexity'. xyu extended n=18 to N=15 seeds (DESIGN.md 31): trend weakened but did not evaporate (9.3%-\u003e6.4%, two-sided Wilcoxon p 0.098-\u003e0.059), still ambiguous. A genuinely distinct third example programme with real room-type diversity at an intermediate room count (not a duplicated-code scale-up) would avoid the interchangeable-room confound and better isolate room count as the driving variable behind the wing-rebuild-fraction hypothesis from f1d (DESIGN.md 23).","status":"in_progress","priority":3,"issue_type":"task","assignee":"Bruno Postle","owner":"bruno@postle.net","created_at":"2026-07-29T09:07:48Z","created_by":"Bruno Postle","updated_at":"2026-07-29T14:05:00Z","started_at":"2026-07-29T14:05:00Z","dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||||
{"id":"homemaker-py-e01","title":"Larger-N harbor-house sweep for c94 beam-width mean improvement","description":"homemaker-py-c94 measured construction_beam_width=4 vs 1 (greedy) end-to-end\non harbor-house at N=5 seeds, budget 1500, n_workers=1: 2 wins / 1 loss / 2\nties, mean fails 56.8 (bw=1) -\u003e 55.4 (bw=4). That's the same small-N,\nmixed-direction shape this log has repeatedly warned produces false signal\n(the \"8sh/1ph/qi6/lj3 pattern\" flagged in DESIGN.md section 23, f1d)\n-- a genuine loss (seed 5) sits alongside the two wins, and N=5 is far\nshort of what f1d's own larger-N confirmation needed (N=15/8) to separate\na real effect from noise.\n\nFollow-up: extend the harbor-house-only comparison to N=15+ seeds at the\nsame protocol (construction_beam_width=4 vs 1, budget 1500, n_workers=1,\ndriver.search from init.dom) to determine whether the mean-improvement\nlean is a real effect or an artefact of seed 2's outlier (67-\u003e52 fails).\nprogramme-house showed zero effect at any width/N tested and does not\nneed re-checking. See DESIGN.md section 29 for full methodology and the\nraw-seed-vs-end-to-end correction this follow-up builds on.","status":"closed","priority":3,"issue_type":"task","assignee":"Bruno Postle","owner":"bruno@postle.net","created_at":"2026-07-28T09:44:38Z","created_by":"Bruno Postle","updated_at":"2026-07-28T23:20:46Z","started_at":"2026-07-28T16:43:56Z","closed_at":"2026-07-28T23:20:46Z","close_reason":"Confirmed null at N=15 (Wilcoxon p=0.84); mean improvement was seed 2's outlier — see DESIGN.md §30","dependencies":[{"issue_id":"homemaker-py-e01","depends_on_id":"homemaker-py-c94","type":"related","created_at":"2026-07-28T10:45:16Z","created_by":"Bruno Postle","metadata":"{}"}],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
{"id":"homemaker-py-e01","title":"Larger-N harbor-house sweep for c94 beam-width mean improvement","description":"homemaker-py-c94 measured construction_beam_width=4 vs 1 (greedy) end-to-end\non harbor-house at N=5 seeds, budget 1500, n_workers=1: 2 wins / 1 loss / 2\nties, mean fails 56.8 (bw=1) -\u003e 55.4 (bw=4). That's the same small-N,\nmixed-direction shape this log has repeatedly warned produces false signal\n(the \"8sh/1ph/qi6/lj3 pattern\" flagged in DESIGN.md section 23, f1d)\n-- a genuine loss (seed 5) sits alongside the two wins, and N=5 is far\nshort of what f1d's own larger-N confirmation needed (N=15/8) to separate\na real effect from noise.\n\nFollow-up: extend the harbor-house-only comparison to N=15+ seeds at the\nsame protocol (construction_beam_width=4 vs 1, budget 1500, n_workers=1,\ndriver.search from init.dom) to determine whether the mean-improvement\nlean is a real effect or an artefact of seed 2's outlier (67-\u003e52 fails).\nprogramme-house showed zero effect at any width/N tested and does not\nneed re-checking. See DESIGN.md section 29 for full methodology and the\nraw-seed-vs-end-to-end correction this follow-up builds on.","status":"closed","priority":3,"issue_type":"task","assignee":"Bruno Postle","owner":"bruno@postle.net","created_at":"2026-07-28T09:44:38Z","created_by":"Bruno Postle","updated_at":"2026-07-28T23:20:46Z","started_at":"2026-07-28T16:43:56Z","closed_at":"2026-07-28T23:20:46Z","close_reason":"Confirmed null at N=15 (Wilcoxon p=0.84); mean improvement was seed 2's outlier — see DESIGN.md §30","dependencies":[{"issue_id":"homemaker-py-e01","depends_on_id":"homemaker-py-c94","type":"related","created_at":"2026-07-28T10:45:16Z","created_by":"Bruno Postle","metadata":"{}"}],"dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||||
{"id":"homemaker-py-cdl","title":"Consider defaulting collapse_global local_search on + expose on evolve --collapse","description":"homemaker-py-9wi added Fitness._two_opt_adjacency_polish (2-opt swap search after the Jacobi adjacency fixpoint), gated behind collapse_global(local_search=True)/homemaker-collapse --local-search, default OFF. Empirical sweep over the 11 harbor-house .dom files: 0 regressions, 1 real improvement (evolved-anneal-3M.dom 21-\u003e19 fails, a genuine mutual-adjacency miss the Jacobi loop couldn't reach). Monotone by construction (only strictly-improving swaps kept) and cheap (\u003c1s on the largest file), so it looks safe to default on, but the sample is small (11 files, one non-synthetic dataset) and evolve.py's --collapse hook (driver.collapse_best) does not expose the flag at all yet. Before flipping the default: (1) run a broader sweep (programme-house + any other example sets) to confirm no regressions elsewhere, (2) add a --collapse-local-search passthrough to evolve.py's CLI alongside driver.collapse_best's **collapse_kw. Low priority -- collapse_finish's keep-better wrapper already makes the current opt-in flag safe to use standalone via homemaker-collapse.","status":"closed","priority":3,"issue_type":"task","assignee":"Bruno Postle","owner":"bruno@postle.net","created_at":"2026-07-26T19:57:32Z","created_by":"Bruno Postle","updated_at":"2026-07-26T22:32:24Z","started_at":"2026-07-26T22:20:41Z","closed_at":"2026-07-26T22:32:24Z","close_reason":"Ran a 46-file A/B sweep (local_search=False vs True in collapse_finish) across harbor-house (12 files) and programme-house (34 files): 0 regressions, 2 improvements (evolved-anneal-3M.dom 21-\u003e19, a82f07068e4408fdd0d5e3dc469a8dee.dom 3-\u003e2 fails), rest identical. Did NOT flip collapse_global's own default (still False) because it is also called every fitness eval via collapse_insearch (qpk) on the unmerged tree -- that hot per-eval path should stay cheap. Instead flipped the two one-shot finish-time call sites to default local_search=True explicitly: homemaker-collapse --local-search (collapse_cmd.py) and new homemaker-evolve --collapse-local-search (evolve.py, threaded through driver.collapse_best's **collapse_kw). All 298 tests pass.","dependency_count":0,"dependent_count":0,"comment_count":0}
|
{"id":"homemaker-py-cdl","title":"Consider defaulting collapse_global local_search on + expose on evolve --collapse","description":"homemaker-py-9wi added Fitness._two_opt_adjacency_polish (2-opt swap search after the Jacobi adjacency fixpoint), gated behind collapse_global(local_search=True)/homemaker-collapse --local-search, default OFF. Empirical sweep over the 11 harbor-house .dom files: 0 regressions, 1 real improvement (evolved-anneal-3M.dom 21-\u003e19 fails, a genuine mutual-adjacency miss the Jacobi loop couldn't reach). Monotone by construction (only strictly-improving swaps kept) and cheap (\u003c1s on the largest file), so it looks safe to default on, but the sample is small (11 files, one non-synthetic dataset) and evolve.py's --collapse hook (driver.collapse_best) does not expose the flag at all yet. Before flipping the default: (1) run a broader sweep (programme-house + any other example sets) to confirm no regressions elsewhere, (2) add a --collapse-local-search passthrough to evolve.py's CLI alongside driver.collapse_best's **collapse_kw. Low priority -- collapse_finish's keep-better wrapper already makes the current opt-in flag safe to use standalone via homemaker-collapse.","status":"closed","priority":3,"issue_type":"task","assignee":"Bruno Postle","owner":"bruno@postle.net","created_at":"2026-07-26T19:57:32Z","created_by":"Bruno Postle","updated_at":"2026-07-26T22:32:24Z","started_at":"2026-07-26T22:20:41Z","closed_at":"2026-07-26T22:32:24Z","close_reason":"Ran a 46-file A/B sweep (local_search=False vs True in collapse_finish) across harbor-house (12 files) and programme-house (34 files): 0 regressions, 2 improvements (evolved-anneal-3M.dom 21-\u003e19, a82f07068e4408fdd0d5e3dc469a8dee.dom 3-\u003e2 fails), rest identical. Did NOT flip collapse_global's own default (still False) because it is also called every fitness eval via collapse_insearch (qpk) on the unmerged tree -- that hot per-eval path should stay cheap. Instead flipped the two one-shot finish-time call sites to default local_search=True explicitly: homemaker-collapse --local-search (collapse_cmd.py) and new homemaker-evolve --collapse-local-search (evolve.py, threaded through driver.collapse_best's **collapse_kw). All 298 tests pass.","dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||||
{"id":"homemaker-py-xyu","title":"Resolve n=18 ruin_recreate trend: larger-N or a non-synthetic third example (homemaker-py-y51 follow-up)","description":"y51's synthetic room-count sweep (DESIGN.md section 24) found no clean monotonic size threshold for ruin_recreate's benefit: n=10 mild win (N=5, ns), n=14 clean null (N=10), n=18 strongest trend (7W/2L/1T, +9.3% mean fails, Wilcoxon p=0.098, N=10) despite sitting between two weaker sizes, n=22 near-null (N=5). Not significant at conventional levels but the largest effect of the four, sandwiched non-monotonically.\n\nTwo possible follow-ups, not mutually exclusive:\n(a) Extend n=18 to N=15+ seeds (matching the N needed for f1d's own programme-house confirmation) to see if the trend firms up or was noise.\n(b) The synthetic sweep scales room count by duplicating already-interchangeable room codes (count: on b1/t1/b2/t2) -- the same mechanism harbor-house itself uses 'to reduce complexity'. A genuinely distinct third example programme (real room-type diversity at an intermediate room count, not a duplicated-code scale-up) would avoid this confound and better isolate room count as the driving variable behind the wing-rebuild-fraction hypothesis.\n\nLow priority -- enable_ruin_recreate's default-OFF status and existing programme-house-scale guidance are unaffected either way.","status":"closed","priority":3,"issue_type":"task","assignee":"Bruno Postle","owner":"bruno@postle.net","created_at":"2026-07-26T14:33:20Z","created_by":"Bruno Postle","updated_at":"2026-07-29T09:08:13Z","started_at":"2026-07-29T06:31:41Z","closed_at":"2026-07-29T09:08:13Z","close_reason":"N=15 confirmation done (option a); DESIGN.md §31. Trend weakened but not resolved; option (b) refiled as homemaker-py-9yx.","dependency_count":0,"dependent_count":0,"comment_count":0}
|
{"id":"homemaker-py-xyu","title":"Resolve n=18 ruin_recreate trend: larger-N or a non-synthetic third example (homemaker-py-y51 follow-up)","description":"y51's synthetic room-count sweep (DESIGN.md section 24) found no clean monotonic size threshold for ruin_recreate's benefit: n=10 mild win (N=5, ns), n=14 clean null (N=10), n=18 strongest trend (7W/2L/1T, +9.3% mean fails, Wilcoxon p=0.098, N=10) despite sitting between two weaker sizes, n=22 near-null (N=5). Not significant at conventional levels but the largest effect of the four, sandwiched non-monotonically.\n\nTwo possible follow-ups, not mutually exclusive:\n(a) Extend n=18 to N=15+ seeds (matching the N needed for f1d's own programme-house confirmation) to see if the trend firms up or was noise.\n(b) The synthetic sweep scales room count by duplicating already-interchangeable room codes (count: on b1/t1/b2/t2) -- the same mechanism harbor-house itself uses 'to reduce complexity'. A genuinely distinct third example programme (real room-type diversity at an intermediate room count, not a duplicated-code scale-up) would avoid this confound and better isolate room count as the driving variable behind the wing-rebuild-fraction hypothesis.\n\nLow priority -- enable_ruin_recreate's default-OFF status and existing programme-house-scale guidance are unaffected either way.","status":"closed","priority":3,"issue_type":"task","assignee":"Bruno Postle","owner":"bruno@postle.net","created_at":"2026-07-26T14:33:20Z","created_by":"Bruno Postle","updated_at":"2026-07-29T09:08:13Z","started_at":"2026-07-29T06:31:41Z","closed_at":"2026-07-29T09:08:13Z","close_reason":"N=15 confirmation done (option a); DESIGN.md §31. Trend weakened but not resolved; option (b) refiled as homemaker-py-9yx.","dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||||
|
|
@ -96,27 +96,27 @@
|
||||||
{"id":"homemaker-py-erc.6","title":"Experiment: inner-loop slack-expansion objective term","description":"Inner-loop counterpart to plot-fill construction. If Diagnostic B shows the inner loop has room to expand leaves into slack but no objective gradient to do so (the scalar rewards hitting target area but not exceeding it where slack exists), add a term/incentive so the ratio optimiser pushes leaf boundaries out to consume neighbouring slack and satisfy size, rather than parking at target.\n\nCONDITIONAL on Diagnostic B: build this only if B localizes the gap to the inner loop (room to expand, no gradient); if B shows construction targets too-small dims, prefer the plot-fill construction sibling. Must preserve the §5.4 inner-loop cliff / §4.9 lexicographic protection — the term sits where it cannot displace the fail-count ordering. A/B vs §12.2 baseline, seeds 0/1/2, 20000 evals, staged, default-OFF. Record DESIGN.md §13.6.","notes":"DEPRIORITISED by Diagnostic B (§13.2). B shows the inner loop CANNOT repair undersize: the slack is depth-driven maldistribution baked into the frozen topology, and the equal-offset ratio DOF cannot shrink a 14x leaf to feed a starved one without trading into shape fails (0.5^n cliff). Wrong DOF and wrong direction — the blocker is slicing POSITION, not a missing expansion reward. Fix belongs upstream in construction/topology (erc.4 re-scoped, erc.3). Keep as a low-priority follow-up only if a depth-balanced construction still leaves a residual size gradient the inner loop could pick up.","status":"closed","priority":4,"issue_type":"feature","owner":"bruno@postle.net","created_at":"2026-06-22T23:16:24Z","created_by":"Bruno Postle","updated_at":"2026-06-28T13:22:22Z","closed_at":"2026-06-28T13:22:22Z","close_reason":"wont-fix (DESIGN §13.7): Diag B (§13.2) showed the inner loop cannot repair undersize (wrong DOF — slicing position, frozen-topology ratios). Superseded by depth-balanced construction (erc.4). Condition unmet.","dependencies":[{"issue_id":"homemaker-py-erc.6","depends_on_id":"homemaker-py-erc","type":"parent-child","created_at":"2026-06-23T00:16:23Z","created_by":"Bruno Postle","metadata":"{}"},{"issue_id":"homemaker-py-erc.6","depends_on_id":"homemaker-py-erc.2","type":"blocks","created_at":"2026-06-23T00:16:47Z","created_by":"Bruno Postle","metadata":"{}"}],"dependency_count":1,"dependent_count":0,"comment_count":0}
|
{"id":"homemaker-py-erc.6","title":"Experiment: inner-loop slack-expansion objective term","description":"Inner-loop counterpart to plot-fill construction. If Diagnostic B shows the inner loop has room to expand leaves into slack but no objective gradient to do so (the scalar rewards hitting target area but not exceeding it where slack exists), add a term/incentive so the ratio optimiser pushes leaf boundaries out to consume neighbouring slack and satisfy size, rather than parking at target.\n\nCONDITIONAL on Diagnostic B: build this only if B localizes the gap to the inner loop (room to expand, no gradient); if B shows construction targets too-small dims, prefer the plot-fill construction sibling. Must preserve the §5.4 inner-loop cliff / §4.9 lexicographic protection — the term sits where it cannot displace the fail-count ordering. A/B vs §12.2 baseline, seeds 0/1/2, 20000 evals, staged, default-OFF. Record DESIGN.md §13.6.","notes":"DEPRIORITISED by Diagnostic B (§13.2). B shows the inner loop CANNOT repair undersize: the slack is depth-driven maldistribution baked into the frozen topology, and the equal-offset ratio DOF cannot shrink a 14x leaf to feed a starved one without trading into shape fails (0.5^n cliff). Wrong DOF and wrong direction — the blocker is slicing POSITION, not a missing expansion reward. Fix belongs upstream in construction/topology (erc.4 re-scoped, erc.3). Keep as a low-priority follow-up only if a depth-balanced construction still leaves a residual size gradient the inner loop could pick up.","status":"closed","priority":4,"issue_type":"feature","owner":"bruno@postle.net","created_at":"2026-06-22T23:16:24Z","created_by":"Bruno Postle","updated_at":"2026-06-28T13:22:22Z","closed_at":"2026-06-28T13:22:22Z","close_reason":"wont-fix (DESIGN §13.7): Diag B (§13.2) showed the inner loop cannot repair undersize (wrong DOF — slicing position, frozen-topology ratios). Superseded by depth-balanced construction (erc.4). Condition unmet.","dependencies":[{"issue_id":"homemaker-py-erc.6","depends_on_id":"homemaker-py-erc","type":"parent-child","created_at":"2026-06-23T00:16:23Z","created_by":"Bruno Postle","metadata":"{}"},{"issue_id":"homemaker-py-erc.6","depends_on_id":"homemaker-py-erc.2","type":"blocks","created_at":"2026-06-23T00:16:47Z","created_by":"Bruno Postle","metadata":"{}"}],"dependency_count":1,"dependent_count":0,"comment_count":0}
|
||||||
{"id":"homemaker-py-erc.5","title":"Experiment: compactness-aware cuts (minimize leaf perimeter/area)","description":"Attacks the #1 factor, crinkliness (346) — a per-leaf perimeter/area property DISTINCT from proportion (aspect ratio). Proportion-aware seeding (leu.2) sizes splits but does not bias toward balanced, square-ish subdivision. Add a KD-tree-style 'keep both children compact' cut rule (prefer the cut orientation/position that minimises summed child perimeter/area) in construction.\n\nCONDITIONAL on Diagnostic A: if A shows per-leaf shape-fail is FLAT across densities (floor intrinsic to slicing density), better cuts at the same leaf count will not pay → this should be closed wont-fix in favour of leaf-sharing. Only build if A shows shape-fail RISES with density. A/B vs §12.2 baseline, seeds 0/1/2, 20000 evals, staged, default-OFF. Record DESIGN.md §13.5.","notes":"DEPRIORITISED by erc.1 verdict (§13.1): per-leaf shape-fail flat vs slicing density and cuts already squarest (_size_divisions_from_targets picks squarest rotation) yet still ~1.8 fails/leaf =\u003e little compactness headroom at fixed leaf count. Floor is intrinsic to leaf COUNT, not cut quality. Revisit only if leaf-sharing (erc.3) underdelivers.","status":"closed","priority":4,"issue_type":"feature","owner":"bruno@postle.net","created_at":"2026-06-22T23:16:21Z","created_by":"Bruno Postle","updated_at":"2026-06-28T13:22:17Z","closed_at":"2026-06-28T13:22:17Z","close_reason":"wont-fix (DESIGN §13.7): Diag A (§13.1) showed the floor is intrinsic to leaf COUNT not cut quality; revisit condition was 'only if leaf-sharing underdelivers' but leaf-sharing OVER-delivered (−32…−39%, §13.3). Condition unmet.","dependencies":[{"issue_id":"homemaker-py-erc.5","depends_on_id":"homemaker-py-erc","type":"parent-child","created_at":"2026-06-23T00:16:21Z","created_by":"Bruno Postle","metadata":"{}"},{"issue_id":"homemaker-py-erc.5","depends_on_id":"homemaker-py-erc.1","type":"blocks","created_at":"2026-06-23T00:16:43Z","created_by":"Bruno Postle","metadata":"{}"}],"dependency_count":1,"dependent_count":0,"comment_count":0}
|
{"id":"homemaker-py-erc.5","title":"Experiment: compactness-aware cuts (minimize leaf perimeter/area)","description":"Attacks the #1 factor, crinkliness (346) — a per-leaf perimeter/area property DISTINCT from proportion (aspect ratio). Proportion-aware seeding (leu.2) sizes splits but does not bias toward balanced, square-ish subdivision. Add a KD-tree-style 'keep both children compact' cut rule (prefer the cut orientation/position that minimises summed child perimeter/area) in construction.\n\nCONDITIONAL on Diagnostic A: if A shows per-leaf shape-fail is FLAT across densities (floor intrinsic to slicing density), better cuts at the same leaf count will not pay → this should be closed wont-fix in favour of leaf-sharing. Only build if A shows shape-fail RISES with density. A/B vs §12.2 baseline, seeds 0/1/2, 20000 evals, staged, default-OFF. Record DESIGN.md §13.5.","notes":"DEPRIORITISED by erc.1 verdict (§13.1): per-leaf shape-fail flat vs slicing density and cuts already squarest (_size_divisions_from_targets picks squarest rotation) yet still ~1.8 fails/leaf =\u003e little compactness headroom at fixed leaf count. Floor is intrinsic to leaf COUNT, not cut quality. Revisit only if leaf-sharing (erc.3) underdelivers.","status":"closed","priority":4,"issue_type":"feature","owner":"bruno@postle.net","created_at":"2026-06-22T23:16:21Z","created_by":"Bruno Postle","updated_at":"2026-06-28T13:22:17Z","closed_at":"2026-06-28T13:22:17Z","close_reason":"wont-fix (DESIGN §13.7): Diag A (§13.1) showed the floor is intrinsic to leaf COUNT not cut quality; revisit condition was 'only if leaf-sharing underdelivers' but leaf-sharing OVER-delivered (−32…−39%, §13.3). Condition unmet.","dependencies":[{"issue_id":"homemaker-py-erc.5","depends_on_id":"homemaker-py-erc","type":"parent-child","created_at":"2026-06-23T00:16:21Z","created_by":"Bruno Postle","metadata":"{}"},{"issue_id":"homemaker-py-erc.5","depends_on_id":"homemaker-py-erc.1","type":"blocks","created_at":"2026-06-23T00:16:43Z","created_by":"Bruno Postle","metadata":"{}"}],"dependency_count":1,"dependent_count":0,"comment_count":0}
|
||||||
{"id":"homemaker-py-2g5","title":"Rebuild occlusion/daylight/sun subsystem in Python (post-Phase-5, after optimisation fully native)","description":"DESIGN.md §6 port scope — a whole subsystem, not a term. quality_daylight (Leaf.pm:281-296) needs Urb::Misc::Sun + Urb::Field::Occlusion (+CIESky); quality_uncrinkliness also takes the occlusion object. Indoor spaces return 1 for daylight; cost is outdoor spaces + crinkliness. Port Sun_horizontal (262980-minute normalisation) and the occlusion wall set from Dom-\u003eWalls.","acceptance_criteria":"Daylight and crinkliness factors match Perl (float tolerance) across the corpus, including multi-storey cases","notes":"Re-scoped 2026-06-12: occlusion disabled in the Urb oracle instead of ported (see homemaker-py-gp2). Native fitness ships with simple crinkliness (illumination factor = 1, in homemaker-py-gnw). This issue is now the eventual Python occlusion rebuild, only after optimisation works entirely in Python. Restores outdoor-daylight and shaded-wall selection pressure.\nReframed 2026-06-17: orthogonal to epic homemaker-py-c4c. This is fitness FIDELITY (restoring daylight + shaded-wall selection pressure to match Perl), not search CAPABILITY — it changes what 'good' means, not the search's ability to find good. It will NOT improve final designs in the sense currently sought. Stays P4, deferred until the topology-search-quality epic lands and optimisation is fully native.","status":"open","priority":4,"issue_type":"feature","owner":"bruno@postle.net","created_at":"2026-06-11T23:38:25Z","created_by":"Bruno Postle","updated_at":"2026-06-17T19:14:48Z","dependency_count":0,"dependent_count":0,"comment_count":0}
|
{"id":"homemaker-py-2g5","title":"Rebuild occlusion/daylight/sun subsystem in Python (post-Phase-5, after optimisation fully native)","description":"DESIGN.md §6 port scope — a whole subsystem, not a term. quality_daylight (Leaf.pm:281-296) needs Urb::Misc::Sun + Urb::Field::Occlusion (+CIESky); quality_uncrinkliness also takes the occlusion object. Indoor spaces return 1 for daylight; cost is outdoor spaces + crinkliness. Port Sun_horizontal (262980-minute normalisation) and the occlusion wall set from Dom-\u003eWalls.","acceptance_criteria":"Daylight and crinkliness factors match Perl (float tolerance) across the corpus, including multi-storey cases","notes":"Re-scoped 2026-06-12: occlusion disabled in the Urb oracle instead of ported (see homemaker-py-gp2). Native fitness ships with simple crinkliness (illumination factor = 1, in homemaker-py-gnw). This issue is now the eventual Python occlusion rebuild, only after optimisation works entirely in Python. Restores outdoor-daylight and shaded-wall selection pressure.\nReframed 2026-06-17: orthogonal to epic homemaker-py-c4c. This is fitness FIDELITY (restoring daylight + shaded-wall selection pressure to match Perl), not search CAPABILITY — it changes what 'good' means, not the search's ability to find good. It will NOT improve final designs in the sense currently sought. Stays P4, deferred until the topology-search-quality epic lands and optimisation is fully native.","status":"open","priority":4,"issue_type":"feature","owner":"bruno@postle.net","created_at":"2026-06-11T23:38:25Z","created_by":"Bruno Postle","updated_at":"2026-06-17T19:14:48Z","dependency_count":0,"dependent_count":0,"comment_count":0}
|
||||||
{"_type":"memory","key":"user-preference-bruno-this-is-a-fedora-system","value":"User preference (Bruno): this is a Fedora system — NEVER install Python packages via pip without asking first; always ask whether to install the rpm via dnf (e.g. python3-cma) before considering pip. Applies to any dependency additions."}
|
|
||||||
{"_type":"memory","key":"correction-to-urb-fitness-bug-memory-bruno-2026","value":"CORRECTION to urb-fitness-bug memory (Bruno, 2026-06-12): 'C' is NOT a 'covered' type — Is_Covered is a geometric predicate (indoor space above). Urb's generic types are canonically UPPERCASE: C=circulation, O=outside, S=sahn (get_space_types qw/C O S/; corpus is 100% uppercase, never 'c'/'o' leaves). The mixed-case designs that fired the latent ratio_type first-match bug were created by homemaker's own operator type pool emitting lowercase 'c'/'o' — fixed: driver/operators now emit uppercase generics only, and class checks use t[0].lower() in 'cos'. The Urb class-sum patch stays as defensive hardening (zero impact on canonical designs). Native port (3y7/gnw): treat type classes case-insensitively, generics canonically uppercase."}
|
|
||||||
{"_type":"memory","key":"unfold-strategy-for-shared-leaves-homemaker-py-8iv","value":"Unfold strategy for shared leaves (homemaker-py-8iv, resolved 2026-07-16): use the BALANCED GRID (operators._grow_balanced/_size_subtree_equal), NOT circulation-aware slicing. Slicing a shared leaf perpendicular to its access edge so every child touches the corridor was implemented + A/B-tested and LOST decisively (150k-eval warm-start polish from evolved-3M: slice 41 fails/3.5e-14 vs grid 25 fails/2.4e-09, grid ahead at every milestone). Reason: k rooms all touching one wall are intrinsically thin slices; that geometric debt (proportion/long/width) is unfixable without topology change, while the grid's squarer children let local search re-route access cheaply via level_retype/place_missing/level_fix. Lesson: at the sharing-\u003eno-sharing transition, prioritise squarer children and leave access to local search; do not reintroduce slicing in Schedule B (kpu)."}
|
|
||||||
{"_type":"memory","key":"collapse-global-94g-and-any-label-usage-optimisation","value":"collapse_global (94g) and any label/usage optimisation CANNOT fix geometry-intrinsic fails. The harbor-house 15-fail best layout contains long-thin cells that are useless whatever room usage is assigned — their width/proportion/crinkliness fails are shape-bound, not label slack. Two consequences: (1) do not over-claim collapse gains — only ~2-3 of that layout's fails are reclaimable relabel slack, the rest are geometry- or building-level bound; (2) the threshold objective must not be tuned to 'pass' a degenerate cell via a permissive room type — a metric-pass on a physically useless space is gaming, not a fix. Real remedies for these are geometry/topology search (cell shape) and circulation placement, filed separately, not the collapse."}
|
|
||||||
{"_type":"memory","key":"cli-tool-style-prefer-python-m-homemaker-module","value":"CLI tool style: prefer python -m homemaker.module --parameters pattern, installable via pip install -e . with pyproject.toml entry_points. Not standalone bin/ scripts."}
|
|
||||||
{"_type":"memory","key":"island-model-psk-14-is-a-null-priming","value":"Island model (psk, §14) is a NULL: priming a population from N converged independent elites + crossover-heavy migration does not beat best-of-N at equal total budget (maple island 124 vs control 116). The child_probe instrument shows WHY: area-matched crossover across independently-converged elites almost never synthesizes (1-3 of ~64 children beat the better parent, max drop 2-5) because the slicing encoding is non-canonical (9gp), so splices are disruptive not combinatorial. Search-machinery null #3 after graded-objective and niching/restarts; residual stays geometry/shape-bound."}
|
|
||||||
{"_type":"memory","key":"strategy-decision-2026-06-12-bruno-occlusion-daylight","value":"Strategy decision 2026-06-12 (Bruno): occlusion/daylight is ORTHOGONAL to building a scalable optimiser. Disable it in Urb (env flag, homemaker-py-gp2) rather than port it; native fitness uses simple crinkliness (illumination factor = 1); rebuild occlusion in Python only after optimisation is fully native (homemaker-py-2g5, now P4). Consequence: all scores change when the flag flips — re-baseline corpus/.score, DESIGN \\$4.5 gains, gate bars at one clean boundary AFTER homemaker-py-1p0 closes; Phase-2 urb-evolve benchmark must run with the same flag."}
|
|
||||||
{"_type":"memory","key":"warm-x0-initialization-bug-pattern-when-a-topology","value":"warm_x0 initialization bug pattern: when a topology operator explicitly sets division ratios on a newly-created node (e.g. compound_fix sets node.division=[0.25,0.25] for t3), parent.ratios has no entry for that node (it was a leaf). warm_x0 defaults it to 0.5, corrupting the inner loop's starting point and making the operator invisible to lex comparison. Fix: only propagate child ratios for nodes where the parent node was NOT already divided; stale hidden nodes revealed by structural mutations (swap flipping b.below) must NOT contribute their pre-writeback values. See driver.py lines 259-267 (fixed 2026-06-14)."}
|
|
||||||
{"_type":"memory","key":"deceptive-valleys-in-topology-search-when-every-single","value":"Deceptive valleys in topology search: when every single-step mutation from a target state passes through a high-fail intermediary (e.g. level_fix displaces a room into 5+ new fails), a compound operator that atomically applies two coordinated changes can escape. Design compound operators to land on the low-fail state directly, bypassing the deceptive gradient. Programme-house example: level_compound_fix atomically moves the level-constrained room AND re-inserts the displaced room adjacent to C in one step (operators.py, 2026-06-14)."}
|
|
||||||
{"_type":"memory","key":"experiment-seeding-pitfall-run-search-scaled-py-s","value":"Experiment seeding pitfall: run_search_scaled.py's default PH_SEED (c964…dom) is a FINISHED programme-house design — passing it warm-starts and floors at ~3 fails, NOT a blank-slate topology search. For blank-slate runs comparable to §11.5/§11.6 baselines, seed from examples/programme-house/init.dom (a bare undivided plot; driver bootstrap auto-triggers only on bare plots). Bit the 6zy sweep — first pass used c964 and falsely showed 3-fail floor across the whole grid."}
|
|
||||||
{"_type":"memory","key":"9o5-multi-use-leaves-is-path-a-superposition","value":"9o5 multi-use leaves is path (a) — superposition as SEARCH RELAXATION that COLLAPSES to specific usage at the end, NOT path (b) loose-fit/no-collapse. Bruno's intent: codes with SIMILAR leaf requirements form an interchangeable equivalence class; during evolution the solver doesn't commit which leaf serves which specific usage (smoother landscape, no fighting over exact leaf usage); at the end the layout is CONDENSED to specific usages by brute-forcing the in-class assignment (3 interchangeable usages over 3 leaves = 3! = 6 combinations to check, pick best). 'Derive automatically' compatibility = requirement-similarity grouping. This reverses the issue's stated 'path b preferred' note."}
|
|
||||||
{"_type":"memory","key":"collapse-global-s-jacobi-adjacency-relaxation-homemaker-py","value":"collapse_global's Jacobi adjacency relaxation (homemaker-py-94g) is a synchronous per-round linear-assignment re-solve, which can 2-cycle indefinitely between two labellings that each satisfy ZERO adjacency requirements even though a permutation satisfying ALL of them exists -- proven on a minimal 4-cell chain (p1-q1-p2-q2, two disjoint adjacency pairs p1\u003c-\u003ep2/q1\u003c-\u003eq2) in test_two_opt_polish_escapes_jacobi_plateau. homemaker-py-9wi added Fitness._two_opt_adjacency_polish: a same-level pairwise-swap local search run after the Jacobi fixpoint, gated behind collapse_global(local_search=True) (default off, exposed as homemaker-collapse --local-search). Monotone by construction (a swap is kept only if it strictly increases total reward). Empirically on the 11 harbor-house evolved-*.dom/3m.dom/materialised-3M.dom layouts: 10 matched Jacobi-only exactly, 0 regressed, and evolved-anneal-3M.dom improved 21-\u003e19 fails (fixed a genuine mutual da1\u003c-\u003ek1 adjacency miss the Jacobi loop couldn't reach)."}
|
|
||||||
{"_type":"memory","key":"homemaker-py-pythonpath-set-pythonpath-home-bruno-src","value":"homemaker-layout PYTHONPATH: package installed as 'homemaker-layout' via pip install -e . so 'import homemaker_layout' works from anywhere without PYTHONPATH. For running tests use 'python -m pytest' from project root /home/bruno/src/homemaker-layout (pyproject.toml adds src/ automatically). Never try pip show homemaker — that's the old homemaker-addon conflict."}
|
|
||||||
{"_type":"memory","key":"proportion-aware-constructive-seeding-leu-2-12-2","value":"Proportion-aware constructive seeding (leu.2/§12.2): sizing seed cuts from target AREAS only regresses (thin slivers wreck aspect); you must ALSO pick each cut's rotation for child squareness. It is a convergence ACCELERATOR via a deeper local optimum around the constructed topology: wins where that topology is roughly right and budget is scarce (harbor -13%, maple -10% at 20k evals) but DELAYS small programmes where the seed must be restructured by undivide (programme-house regresses at fixed budget, yet reaches the floor given budget - speed, not asymptote). Default-on. Also: n_storeys must honour storey_minimum, not just level: keys (programme-house storey_minimum:2, all rooms level:0 - was seeded 1 storey short; cq1)."}
|
|
||||||
{"_type":"memory","key":"adjacency-in-binary-slicing-tree-is-structural-not","value":"Adjacency in binary slicing tree is structural, not geometric: the inner-loop NM cannot fix topological adjacency failures. Two paths exist: (1) tree-sibling adjacency — a node is adjacent to its sibling in the tree; (2) cross-zone geometric adjacency — leaves from different subtrees that happen to share a boundary. Staircase/adjacency fails require a topology mutation that changes which nodes are siblings or which zones touch. This was proved empirically on programme-house: staircase fail from rot=0 layout could not be fixed by NM but was fixed by level_retype creating a two-C topology (2026-06-14/15)."}
|
{"_type":"memory","key":"adjacency-in-binary-slicing-tree-is-structural-not","value":"Adjacency in binary slicing tree is structural, not geometric: the inner-loop NM cannot fix topological adjacency failures. Two paths exist: (1) tree-sibling adjacency — a node is adjacent to its sibling in the tree; (2) cross-zone geometric adjacency — leaves from different subtrees that happen to share a boundary. Staircase/adjacency fails require a topology mutation that changes which nodes are siblings or which zones touch. This was proved empirically on programme-house: staircase fail from rot=0 layout could not be fixed by NM but was fixed by level_retype creating a two-C topology (2026-06-14/15)."}
|
||||||
{"_type":"memory","key":"urb-oracle-nondeterminism-urb-fitness-pl-output-varies","value":"Urb oracle nondeterminism: urb-fitness.pl output varies run-to-run from Perl hash-order randomisation — .fails line ORDER shuffles (compare sorted, use oracle.Score.fail_lines) and the score float can flip by ~1 ULP (compare with math.isclose rel_tol=1e-12, never ==). Not a batching artifact; affects single runs too. Matters for the Phase 3 native-fitness parity gate (homemaker-py-uxz)."}
|
{"_type":"memory","key":"homemaker-py-pythonpath-set-pythonpath-home-bruno-src","value":"homemaker-layout PYTHONPATH: package installed as 'homemaker-layout' via pip install -e . so 'import homemaker_layout' works from anywhere without PYTHONPATH. For running tests use 'python -m pytest' from project root /home/bruno/src/homemaker-layout (pyproject.toml adds src/ automatically). Never try pip show homemaker — that's the old homemaker-addon conflict."}
|
||||||
{"_type":"memory","key":"ld2-13-6-interior-o-seed-diagnostic-all","value":"ld2/§13.6 interior-O seed diagnostic: ALL crinkliness fails in the constructed bal+share seed are UNDER-exposed (crink\u003c0.62, landlocked rooms with no facade + no uncovered-O neighbour) — zero over-exposed sliver fails. So the erc crinkliness residual is genuine under-daylighting, validating the interior light-well premise. Default outside_divisor=6 was too sparse (null: harbor 147-\u003e142, crinkliness even rose). odiv=3 is the seed-optimal joint setting: harbor seed fails 147-\u003e129 (-18), maple 219-\u003e206 (-14), landlocked fails drop, at cost of more leaves (harbor +4, maple +8). Because it ADDS leaves it carries the §13.4 wash-out risk; A/B to convergence pending."}
|
{"_type":"memory","key":"multi-storey-staircase-consistency-when-dividing-or-retyping","value":"Multi-storey staircase consistency: when dividing or retyping a circulation (C) leaf at one level, the same structural change should be propagated to the matching leaf on ALL other storeys so the stair core path is maintained. The optimizer cannot fix staircase disruptions through trial-and-error geometry alone — it requires a synchronized multi-level operator that applies the same topology change to every storey simultaneously."}
|
||||||
|
{"_type":"memory","key":"strategy-decision-2026-06-12-bruno-occlusion-daylight","value":"Strategy decision 2026-06-12 (Bruno): occlusion/daylight is ORTHOGONAL to building a scalable optimiser. Disable it in Urb (env flag, homemaker-py-gp2) rather than port it; native fitness uses simple crinkliness (illumination factor = 1); rebuild occlusion in Python only after optimisation is fully native (homemaker-py-2g5, now P4). Consequence: all scores change when the flag flips — re-baseline corpus/.score, DESIGN \\$4.5 gains, gate bars at one clean boundary AFTER homemaker-py-1p0 closes; Phase-2 urb-evolve benchmark must run with the same flag."}
|
||||||
|
{"_type":"memory","key":"cli-tool-style-prefer-python-m-homemaker-module","value":"CLI tool style: prefer python -m homemaker.module --parameters pattern, installable via pip install -e . with pyproject.toml entry_points. Not standalone bin/ scripts."}
|
||||||
|
{"_type":"memory","key":"collapse-global-s-jacobi-adjacency-relaxation-homemaker-py","value":"collapse_global's Jacobi adjacency relaxation (homemaker-py-94g) is a synchronous per-round linear-assignment re-solve, which can 2-cycle indefinitely between two labellings that each satisfy ZERO adjacency requirements even though a permutation satisfying ALL of them exists -- proven on a minimal 4-cell chain (p1-q1-p2-q2, two disjoint adjacency pairs p1\u003c-\u003ep2/q1\u003c-\u003eq2) in test_two_opt_polish_escapes_jacobi_plateau. homemaker-py-9wi added Fitness._two_opt_adjacency_polish: a same-level pairwise-swap local search run after the Jacobi fixpoint, gated behind collapse_global(local_search=True) (default off, exposed as homemaker-collapse --local-search). Monotone by construction (a swap is kept only if it strictly increases total reward). Empirically on the 11 harbor-house evolved-*.dom/3m.dom/materialised-3M.dom layouts: 10 matched Jacobi-only exactly, 0 regressed, and evolved-anneal-3M.dom improved 21-\u003e19 fails (fixed a genuine mutual da1\u003c-\u003ek1 adjacency miss the Jacobi loop couldn't reach)."}
|
||||||
|
{"_type":"memory","key":"experiment-seeding-pitfall-run-search-scaled-py-s","value":"Experiment seeding pitfall: run_search_scaled.py's default PH_SEED (c964…dom) is a FINISHED programme-house design — passing it warm-starts and floors at ~3 fails, NOT a blank-slate topology search. For blank-slate runs comparable to §11.5/§11.6 baselines, seed from examples/programme-house/init.dom (a bare undivided plot; driver bootstrap auto-triggers only on bare plots). Bit the 6zy sweep — first pass used c964 and falsely showed 3-fail floor across the whole grid."}
|
||||||
|
{"_type":"memory","key":"programme-house-optimisation-result-2026-06-14-15","value":"Programme-house optimisation result (2026-06-14/15): best achievable is 1 fail (l1 wrong level, score ~0.005). 0 fails is geometrically impossible: l1 (min 27m²) must occupy ll (~23m²) at level 0, which eliminates the t3-adj-C provider; dividing ll into lll(l1)+llr(C) gives llr proportion ~6:1 (fails). Python memetic optimizer achieves 1 fail in 50k evals vs Perl optimiser's 2-3 fails. Winning topology: TWO C nodes at level 0 — ll(C) for t3-adj-C via geometric contact, rl(C) for staircase via tree-sibling adjacency to rrr(O). Best .dom: scratch/from-warmstart-fixed.dom and scratch/from-compound3-fixed.dom."}
|
||||||
|
{"_type":"memory","key":"warm-x0-initialization-bug-pattern-when-a-topology","value":"warm_x0 initialization bug pattern: when a topology operator explicitly sets division ratios on a newly-created node (e.g. compound_fix sets node.division=[0.25,0.25] for t3), parent.ratios has no entry for that node (it was a leaf). warm_x0 defaults it to 0.5, corrupting the inner loop's starting point and making the operator invisible to lex comparison. Fix: only propagate child ratios for nodes where the parent node was NOT already divided; stale hidden nodes revealed by structural mutations (swap flipping b.below) must NOT contribute their pre-writeback values. See driver.py lines 259-267 (fixed 2026-06-14)."}
|
||||||
{"_type":"memory","key":"never-use-corpus-filenames-candidate-001-dom-candidate","value":"Never use corpus filenames (candidate-001.dom, candidate-002.dom, generated.dom, init.dom, etc.) as --output targets when running experiments. These are test fixtures. Always write experimental outputs to scratch/ or a timestamped path. Lesson from 2026-06-14: warm-start runs overwrote candidate-001/002.dom and broke graph tests."}
|
{"_type":"memory","key":"never-use-corpus-filenames-candidate-001-dom-candidate","value":"Never use corpus filenames (candidate-001.dom, candidate-002.dom, generated.dom, init.dom, etc.) as --output targets when running experiments. These are test fixtures. Always write experimental outputs to scratch/ or a timestamped path. Lesson from 2026-06-14: warm-start runs overwrote candidate-001/002.dom and broke graph tests."}
|
||||||
{"_type":"memory","key":"run-to-run-reproducibility-in-homemaker-layout-serial","value":"Run-to-run reproducibility in homemaker-layout: serial search (workers=1) is byte-for-byte deterministic; parallel (workers\u003e1) is now deterministic too AFTER fixing driver._run_batch to admit futures in submission order (was as_completed/completion order, bug xcy). Reproducibility holds only for a FIXED worker count — serial vs parallel differ because children-per-iteration is 1 vs n_workers (different batch granularity), which is expected, not a bug. The constructive seeder was NEVER nondeterministic: _assign_adjacency_aware has unique idx tiebreaks; comparing topologies with Python builtin hash() of the signature STRING is invalid (PYTHONHASHSEED salts str hashing per process) — use a stable hash (sha1) or genome.signature equality."}
|
{"_type":"memory","key":"run-to-run-reproducibility-in-homemaker-layout-serial","value":"Run-to-run reproducibility in homemaker-layout: serial search (workers=1) is byte-for-byte deterministic; parallel (workers\u003e1) is now deterministic too AFTER fixing driver._run_batch to admit futures in submission order (was as_completed/completion order, bug xcy). Reproducibility holds only for a FIXED worker count — serial vs parallel differ because children-per-iteration is 1 vs n_workers (different batch granularity), which is expected, not a bug. The constructive seeder was NEVER nondeterministic: _assign_adjacency_aware has unique idx tiebreaks; comparing topologies with Python builtin hash() of the signature STRING is invalid (PYTHONHASHSEED salts str hashing per process) — use a stable hash (sha1) or genome.signature equality."}
|
||||||
{"_type":"memory","key":"experiment-harness-gotcha-the-leaf-sharing-relaxed-objective","value":"Experiment harness gotcha: the leaf-sharing RELAXED objective (§13.3) is injected ONLY by monkeypatching fitness.load_config in the parent process (run_staged_search.py / probe scripts). This is parent-process-only and does NOT propagate into ProcessPoolExecutor workers (n_workers\u003e1), which re-import fitness fresh and score under the STRICT on-disk patterns.config -\u003e r.n_fails MISMATCH (worker strict vs parent relaxed re-score). ALL §13.x floor runs were therefore SERIAL. Any future PARALLEL leaf-sharing experiment will silently mis-score until leaf_sharing lives on disk/CLI (tracked: homemaker-py-x3b). The parallel driver itself is correct; both paths score via load_config(programme_dir)."}
|
{"_type":"memory","key":"9o5-multi-use-leaves-is-path-a-superposition","value":"9o5 multi-use leaves is path (a) — superposition as SEARCH RELAXATION that COLLAPSES to specific usage at the end, NOT path (b) loose-fit/no-collapse. Bruno's intent: codes with SIMILAR leaf requirements form an interchangeable equivalence class; during evolution the solver doesn't commit which leaf serves which specific usage (smoother landscape, no fighting over exact leaf usage); at the end the layout is CONDENSED to specific usages by brute-forcing the in-class assignment (3 interchangeable usages over 3 leaves = 3! = 6 combinations to check, pick best). 'Derive automatically' compatibility = requirement-similarity grouping. This reverses the issue's stated 'path b preferred' note."}
|
||||||
{"_type":"memory","key":"multi-storey-staircase-consistency-when-dividing-or-retyping","value":"Multi-storey staircase consistency: when dividing or retyping a circulation (C) leaf at one level, the same structural change should be propagated to the matching leaf on ALL other storeys so the stair core path is maintained. The optimizer cannot fix staircase disruptions through trial-and-error geometry alone — it requires a synchronized multi-level operator that applies the same topology change to every storey simultaneously."}
|
{"_type":"memory","key":"correction-to-urb-fitness-bug-memory-bruno-2026","value":"CORRECTION to urb-fitness-bug memory (Bruno, 2026-06-12): 'C' is NOT a 'covered' type — Is_Covered is a geometric predicate (indoor space above). Urb's generic types are canonically UPPERCASE: C=circulation, O=outside, S=sahn (get_space_types qw/C O S/; corpus is 100% uppercase, never 'c'/'o' leaves). The mixed-case designs that fired the latent ratio_type first-match bug were created by homemaker's own operator type pool emitting lowercase 'c'/'o' — fixed: driver/operators now emit uppercase generics only, and class checks use t[0].lower() in 'cos'. The Urb class-sum patch stays as defensive hardening (zero impact on canonical designs). Native port (3y7/gnw): treat type classes case-insensitively, generics canonically uppercase."}
|
||||||
{"_type":"memory","key":"homemaker-py-3l6-fix-leaf-sharing-evolve-runs","value":"homemaker-py-3l6 fix: leaf-sharing evolve runs now auto-finish before write via driver.polish_finish — unfold_shared_leaves() then a warm-started leaf_sharing=False polish search (--polish-budget, default budget//2). Makes the written .dom honest under canonical homemaker-fitness (internal==canonical when leaf_sharing off). Interrupt path forces polish_budget=0 (unfold+rescore only). This is yaa's unfold-then-polish, made automatic; Schedule B annealing is still kpu."}
|
{"_type":"memory","key":"unfold-strategy-for-shared-leaves-homemaker-py-8iv","value":"Unfold strategy for shared leaves (homemaker-py-8iv, resolved 2026-07-16): use the BALANCED GRID (operators._grow_balanced/_size_subtree_equal), NOT circulation-aware slicing. Slicing a shared leaf perpendicular to its access edge so every child touches the corridor was implemented + A/B-tested and LOST decisively (150k-eval warm-start polish from evolved-3M: slice 41 fails/3.5e-14 vs grid 25 fails/2.4e-09, grid ahead at every milestone). Reason: k rooms all touching one wall are intrinsically thin slices; that geometric debt (proportion/long/width) is unfixable without topology change, while the grid's squarer children let local search re-route access cheaply via level_retype/place_missing/level_fix. Lesson: at the sharing-\u003eno-sharing transition, prioritise squarer children and leave access to local search; do not reintroduce slicing in Schedule B (kpu)."}
|
||||||
{"_type":"memory","key":"programme-house-optimisation-result-2026-06-14-15","value":"Programme-house optimisation result (2026-06-14/15): best achievable is 1 fail (l1 wrong level, score ~0.005). 0 fails is geometrically impossible: l1 (min 27m²) must occupy ll (~23m²) at level 0, which eliminates the t3-adj-C provider; dividing ll into lll(l1)+llr(C) gives llr proportion ~6:1 (fails). Python memetic optimizer achieves 1 fail in 50k evals vs Perl optimiser's 2-3 fails. Winning topology: TWO C nodes at level 0 — ll(C) for t3-adj-C via geometric contact, rl(C) for staircase via tree-sibling adjacency to rrr(O). Best .dom: scratch/from-warmstart-fixed.dom and scratch/from-compound3-fixed.dom."}
|
|
||||||
{"_type":"memory","key":"urb-fitness-bug-found-fixed-2026-06-12","value":"Urb fitness bug found+fixed 2026-06-12 (patch in /home/bruno/src/urb, uncommitted): ProgrammeDriven.pm ratio_o/ratio_type grepped case-insensitively over the ratios hash and took the FIRST key — nondeterministic (x4.5 score swings) for designs with mixed-case type classes (both 'c' circulation and 'C' covered). Fixed to SUM the class (matches Is_Circulation//Is_Outside semantics); 35/35 corpus scores unchanged. CRITICAL for homemaker-py-3y7/gnw: the native port must implement class-SUM ratios. Building.pm has the same unpatched pattern (site-driven path, not used by our oracle). Also: the memetic search reward-hacked this bug before the fix — search results predating it are noise artifacts."}
|
{"_type":"memory","key":"urb-fitness-bug-found-fixed-2026-06-12","value":"Urb fitness bug found+fixed 2026-06-12 (patch in /home/bruno/src/urb, uncommitted): ProgrammeDriven.pm ratio_o/ratio_type grepped case-insensitively over the ratios hash and took the FIRST key — nondeterministic (x4.5 score swings) for designs with mixed-case type classes (both 'c' circulation and 'C' covered). Fixed to SUM the class (matches Is_Circulation//Is_Outside semantics); 35/35 corpus scores unchanged. CRITICAL for homemaker-py-3y7/gnw: the native port must implement class-SUM ratios. Building.pm has the same unpatched pattern (site-driven path, not used by our oracle). Also: the memetic search reward-hacked this bug before the fix — search results predating it are noise artifacts."}
|
||||||
|
{"_type":"memory","key":"urb-oracle-nondeterminism-urb-fitness-pl-output-varies","value":"Urb oracle nondeterminism: urb-fitness.pl output varies run-to-run from Perl hash-order randomisation — .fails line ORDER shuffles (compare sorted, use oracle.Score.fail_lines) and the score float can flip by ~1 ULP (compare with math.isclose rel_tol=1e-12, never ==). Not a batching artifact; affects single runs too. Matters for the Phase 3 native-fitness parity gate (homemaker-py-uxz)."}
|
||||||
|
{"_type":"memory","key":"collapse-global-94g-and-any-label-usage-optimisation","value":"collapse_global (94g) and any label/usage optimisation CANNOT fix geometry-intrinsic fails. The harbor-house 15-fail best layout contains long-thin cells that are useless whatever room usage is assigned — their width/proportion/crinkliness fails are shape-bound, not label slack. Two consequences: (1) do not over-claim collapse gains — only ~2-3 of that layout's fails are reclaimable relabel slack, the rest are geometry- or building-level bound; (2) the threshold objective must not be tuned to 'pass' a degenerate cell via a permissive room type — a metric-pass on a physically useless space is gaming, not a fix. Real remedies for these are geometry/topology search (cell shape) and circulation placement, filed separately, not the collapse."}
|
||||||
|
{"_type":"memory","key":"island-model-psk-14-is-a-null-priming","value":"Island model (psk, §14) is a NULL: priming a population from N converged independent elites + crossover-heavy migration does not beat best-of-N at equal total budget (maple island 124 vs control 116). The child_probe instrument shows WHY: area-matched crossover across independently-converged elites almost never synthesizes (1-3 of ~64 children beat the better parent, max drop 2-5) because the slicing encoding is non-canonical (9gp), so splices are disruptive not combinatorial. Search-machinery null #3 after graded-objective and niching/restarts; residual stays geometry/shape-bound."}
|
||||||
|
{"_type":"memory","key":"user-preference-bruno-this-is-a-fedora-system","value":"User preference (Bruno): this is a Fedora system — NEVER install Python packages via pip without asking first; always ask whether to install the rpm via dnf (e.g. python3-cma) before considering pip. Applies to any dependency additions."}
|
||||||
|
{"_type":"memory","key":"experiment-harness-gotcha-the-leaf-sharing-relaxed-objective","value":"Experiment harness gotcha: the leaf-sharing RELAXED objective (§13.3) is injected ONLY by monkeypatching fitness.load_config in the parent process (run_staged_search.py / probe scripts). This is parent-process-only and does NOT propagate into ProcessPoolExecutor workers (n_workers\u003e1), which re-import fitness fresh and score under the STRICT on-disk patterns.config -\u003e r.n_fails MISMATCH (worker strict vs parent relaxed re-score). ALL §13.x floor runs were therefore SERIAL. Any future PARALLEL leaf-sharing experiment will silently mis-score until leaf_sharing lives on disk/CLI (tracked: homemaker-py-x3b). The parallel driver itself is correct; both paths score via load_config(programme_dir)."}
|
||||||
|
{"_type":"memory","key":"homemaker-py-3l6-fix-leaf-sharing-evolve-runs","value":"homemaker-py-3l6 fix: leaf-sharing evolve runs now auto-finish before write via driver.polish_finish — unfold_shared_leaves() then a warm-started leaf_sharing=False polish search (--polish-budget, default budget//2). Makes the written .dom honest under canonical homemaker-fitness (internal==canonical when leaf_sharing off). Interrupt path forces polish_budget=0 (unfold+rescore only). This is yaa's unfold-then-polish, made automatic; Schedule B annealing is still kpu."}
|
||||||
|
{"_type":"memory","key":"deceptive-valleys-in-topology-search-when-every-single","value":"Deceptive valleys in topology search: when every single-step mutation from a target state passes through a high-fail intermediary (e.g. level_fix displaces a room into 5+ new fails), a compound operator that atomically applies two coordinated changes can escape. Design compound operators to land on the low-fail state directly, bypassing the deceptive gradient. Programme-house example: level_compound_fix atomically moves the level-constrained room AND re-inserts the displaced room adjacent to C in one step (operators.py, 2026-06-14)."}
|
||||||
|
{"_type":"memory","key":"ld2-13-6-interior-o-seed-diagnostic-all","value":"ld2/§13.6 interior-O seed diagnostic: ALL crinkliness fails in the constructed bal+share seed are UNDER-exposed (crink\u003c0.62, landlocked rooms with no facade + no uncovered-O neighbour) — zero over-exposed sliver fails. So the erc crinkliness residual is genuine under-daylighting, validating the interior light-well premise. Default outside_divisor=6 was too sparse (null: harbor 147-\u003e142, crinkliness even rose). odiv=3 is the seed-optimal joint setting: harbor seed fails 147-\u003e129 (-18), maple 219-\u003e206 (-14), landlocked fails drop, at cost of more leaves (harbor +4, maple +8). Because it ADDS leaves it carries the §13.4 wash-out risk; A/B to convergence pending."}
|
||||||
|
{"_type":"memory","key":"proportion-aware-constructive-seeding-leu-2-12-2","value":"Proportion-aware constructive seeding (leu.2/§12.2): sizing seed cuts from target AREAS only regresses (thin slivers wreck aspect); you must ALSO pick each cut's rotation for child squareness. It is a convergence ACCELERATOR via a deeper local optimum around the constructed topology: wins where that topology is roughly right and budget is scarce (harbor -13%, maple -10% at 20k evals) but DELAYS small programmes where the seed must be restructured by undivide (programme-house regresses at fixed budget, yet reaches the floor given budget - speed, not asymptote). Default-on. Also: n_storeys must honour storey_minimum, not just level: keys (programme-house storey_minimum:2, all rooms level:0 - was seeded 1 storey short; cq1)."}
|
||||||
|
|
|
||||||
21
examples/health-centre/init.dom
Normal file
21
examples/health-centre/init.dom
Normal file
|
|
@ -0,0 +1,21 @@
|
||||||
|
---
|
||||||
|
node:
|
||||||
|
- - -0.40619466787232916
|
||||||
|
- 7.945534625317068
|
||||||
|
- - 12.453678259018824
|
||||||
|
- 11.219717050727425
|
||||||
|
- - 8.942638574000743
|
||||||
|
- 25.206100654545047
|
||||||
|
- - -4.223021280218349
|
||||||
|
- 22.57415280833146
|
||||||
|
perimeter:
|
||||||
|
a: private
|
||||||
|
b: ~
|
||||||
|
c: ~
|
||||||
|
d: ~
|
||||||
|
type: O
|
||||||
|
rotation: 0
|
||||||
|
height: 3
|
||||||
|
elevation: 0.0
|
||||||
|
wall_inner: 0.08
|
||||||
|
wall_outer: 0.25
|
||||||
327
examples/health-centre/patterns.config
Normal file
327
examples/health-centre/patterns.config
Normal file
|
|
@ -0,0 +1,327 @@
|
||||||
|
---
|
||||||
|
# Health Centre - Non-synthetic third example programme (homemaker-py-9yx)
|
||||||
|
#
|
||||||
|
# y51's synthetic n=10/14/18/22 sweep (DESIGN.md 24, extended by xyu 31) scales
|
||||||
|
# room count by duplicating a handful of already-interchangeable programme-house
|
||||||
|
# codes (b1/t1/b2/t2/l1) via `count:`. harbor-house has real room-type diversity
|
||||||
|
# (16 distinct codes) but is out of range at 37 room instances, and its own
|
||||||
|
# result stayed null-to-negative -- so it cannot distinguish "the effect needs
|
||||||
|
# more rooms than harbor-house has" from "the effect never existed outside the
|
||||||
|
# duplicated-code mechanism". This programme fills the gap: a genuinely
|
||||||
|
# different building type (a small primary-care health centre, not a house or
|
||||||
|
# a dormitory/co-housing facility) with 19 distinct, individually-sized room
|
||||||
|
# codes at n=20 room instances -- matching xyu's own n=18 test point without
|
||||||
|
# leaning on `count:` as the scaling knob (only one deliberate, realistic
|
||||||
|
# duplication: two public WCs).
|
||||||
|
#
|
||||||
|
# Code conventions (per maple-court, homemaker-py-leu.1): generic c/o/s are
|
||||||
|
# reserved for circulation / outside / sahn in fitness.py's get_space_params
|
||||||
|
# (any code starting with 's' silently falls back to the *_outside defaults
|
||||||
|
# instead of its own size/width/proportion targets) -- so no room code here
|
||||||
|
# starts with c, o, or s.
|
||||||
|
|
||||||
|
# Building programme: small primary-care health centre
|
||||||
|
spaces:
|
||||||
|
# ---- PUBLIC / RECEPTION ----
|
||||||
|
rc1:
|
||||||
|
name: Reception
|
||||||
|
size:
|
||||||
|
- 10.0
|
||||||
|
- 2.0
|
||||||
|
width:
|
||||||
|
- 2.9
|
||||||
|
- 0.6
|
||||||
|
proportion:
|
||||||
|
- 1.6
|
||||||
|
- 0.5
|
||||||
|
level: 0
|
||||||
|
adjacency:
|
||||||
|
- c
|
||||||
|
- o
|
||||||
|
|
||||||
|
wa1:
|
||||||
|
name: Waiting Room
|
||||||
|
size:
|
||||||
|
- 28.0
|
||||||
|
- 5.0
|
||||||
|
width:
|
||||||
|
- 5.0
|
||||||
|
- 1.0
|
||||||
|
proportion:
|
||||||
|
- 1.8
|
||||||
|
- 0.5
|
||||||
|
level: 0
|
||||||
|
adjacency:
|
||||||
|
- c
|
||||||
|
- o
|
||||||
|
- rc1
|
||||||
|
|
||||||
|
ph1:
|
||||||
|
name: Pharmacy / Dispensary
|
||||||
|
size:
|
||||||
|
- 12.0
|
||||||
|
- 2.0
|
||||||
|
width:
|
||||||
|
- 3.1
|
||||||
|
- 0.6
|
||||||
|
proportion:
|
||||||
|
- 1.6
|
||||||
|
- 0.5
|
||||||
|
level: 0
|
||||||
|
adjacency:
|
||||||
|
- c
|
||||||
|
- o
|
||||||
|
- wa1
|
||||||
|
|
||||||
|
# ---- CLINICAL ----
|
||||||
|
gp1:
|
||||||
|
name: GP Consulting Room
|
||||||
|
size:
|
||||||
|
- 14.0
|
||||||
|
- 2.0
|
||||||
|
width:
|
||||||
|
- 3.2
|
||||||
|
- 0.6
|
||||||
|
proportion:
|
||||||
|
- 1.4
|
||||||
|
- 0.4
|
||||||
|
adjacency:
|
||||||
|
- c
|
||||||
|
|
||||||
|
ms1:
|
||||||
|
name: Minor Surgery Room
|
||||||
|
size:
|
||||||
|
- 20.0
|
||||||
|
- 3.0
|
||||||
|
width:
|
||||||
|
- 4.7
|
||||||
|
- 0.8
|
||||||
|
proportion:
|
||||||
|
- 1.3
|
||||||
|
- 0.4
|
||||||
|
adjacency:
|
||||||
|
- c
|
||||||
|
|
||||||
|
de1:
|
||||||
|
name: Dental Surgery
|
||||||
|
size:
|
||||||
|
- 18.0
|
||||||
|
- 3.0
|
||||||
|
width:
|
||||||
|
- 4.6
|
||||||
|
- 0.7
|
||||||
|
proportion:
|
||||||
|
- 1.5
|
||||||
|
- 0.4
|
||||||
|
adjacency:
|
||||||
|
- c
|
||||||
|
- zt1
|
||||||
|
|
||||||
|
zt1:
|
||||||
|
name: Sterilisation Room
|
||||||
|
size:
|
||||||
|
- 6.0
|
||||||
|
- 1.0
|
||||||
|
width:
|
||||||
|
- 1.6
|
||||||
|
- 0.4
|
||||||
|
proportion:
|
||||||
|
- 1.6
|
||||||
|
- 0.4
|
||||||
|
adjacency:
|
||||||
|
- c
|
||||||
|
- de1
|
||||||
|
|
||||||
|
pt1:
|
||||||
|
name: Physiotherapy Room
|
||||||
|
size:
|
||||||
|
- 24.0
|
||||||
|
- 4.0
|
||||||
|
width:
|
||||||
|
- 4.8
|
||||||
|
- 0.8
|
||||||
|
proportion:
|
||||||
|
- 1.6
|
||||||
|
- 0.5
|
||||||
|
adjacency:
|
||||||
|
- c
|
||||||
|
|
||||||
|
qr1:
|
||||||
|
name: Counselling Room
|
||||||
|
size:
|
||||||
|
- 9.0
|
||||||
|
- 1.5
|
||||||
|
width:
|
||||||
|
- 2.6
|
||||||
|
- 0.5
|
||||||
|
proportion:
|
||||||
|
- 1.4
|
||||||
|
- 0.4
|
||||||
|
adjacency:
|
||||||
|
- c
|
||||||
|
|
||||||
|
tr1:
|
||||||
|
name: Treatment Room
|
||||||
|
size:
|
||||||
|
- 16.0
|
||||||
|
- 2.5
|
||||||
|
width:
|
||||||
|
- 3.3
|
||||||
|
- 0.6
|
||||||
|
proportion:
|
||||||
|
- 1.4
|
||||||
|
- 0.4
|
||||||
|
adjacency:
|
||||||
|
- c
|
||||||
|
|
||||||
|
# ---- ADMIN / STAFF ----
|
||||||
|
mo1:
|
||||||
|
name: Manager's Office
|
||||||
|
size:
|
||||||
|
- 10.0
|
||||||
|
- 1.5
|
||||||
|
width:
|
||||||
|
- 2.8
|
||||||
|
- 0.5
|
||||||
|
proportion:
|
||||||
|
- 1.5
|
||||||
|
- 0.4
|
||||||
|
adjacency:
|
||||||
|
- c
|
||||||
|
|
||||||
|
ao1:
|
||||||
|
name: Admin Office
|
||||||
|
size:
|
||||||
|
- 14.0
|
||||||
|
- 2.0
|
||||||
|
width:
|
||||||
|
- 3.0
|
||||||
|
- 0.6
|
||||||
|
proportion:
|
||||||
|
- 1.6
|
||||||
|
- 0.5
|
||||||
|
adjacency:
|
||||||
|
- c
|
||||||
|
|
||||||
|
re1:
|
||||||
|
name: Records Room
|
||||||
|
size:
|
||||||
|
- 7.0
|
||||||
|
- 1.0
|
||||||
|
width:
|
||||||
|
- 1.7
|
||||||
|
- 0.4
|
||||||
|
proportion:
|
||||||
|
- 1.6
|
||||||
|
- 0.4
|
||||||
|
adjacency:
|
||||||
|
- c
|
||||||
|
- ao1
|
||||||
|
|
||||||
|
br1:
|
||||||
|
name: Staff Room
|
||||||
|
size:
|
||||||
|
- 16.0
|
||||||
|
- 2.5
|
||||||
|
width:
|
||||||
|
- 3.4
|
||||||
|
- 0.6
|
||||||
|
proportion:
|
||||||
|
- 1.5
|
||||||
|
- 0.4
|
||||||
|
adjacency:
|
||||||
|
- c
|
||||||
|
|
||||||
|
kt1:
|
||||||
|
name: Staff Kitchenette
|
||||||
|
size:
|
||||||
|
- 8.0
|
||||||
|
- 1.5
|
||||||
|
width:
|
||||||
|
- 2.7
|
||||||
|
- 0.4
|
||||||
|
proportion:
|
||||||
|
- 1.5
|
||||||
|
- 0.4
|
||||||
|
adjacency:
|
||||||
|
- c
|
||||||
|
- br1
|
||||||
|
|
||||||
|
# ---- SERVICE ----
|
||||||
|
me1:
|
||||||
|
name: Plant / Mechanical Room
|
||||||
|
size:
|
||||||
|
- 9.0
|
||||||
|
- 1.5
|
||||||
|
width:
|
||||||
|
- 1.9
|
||||||
|
- 0.4
|
||||||
|
proportion:
|
||||||
|
- 1.7
|
||||||
|
- 0.4
|
||||||
|
adjacency:
|
||||||
|
- c
|
||||||
|
|
||||||
|
dp1:
|
||||||
|
name: General Storage
|
||||||
|
size:
|
||||||
|
- 8.0
|
||||||
|
- 1.5
|
||||||
|
width:
|
||||||
|
- 1.8
|
||||||
|
- 0.4
|
||||||
|
proportion:
|
||||||
|
- 1.7
|
||||||
|
- 0.4
|
||||||
|
adjacency:
|
||||||
|
- c
|
||||||
|
|
||||||
|
t9:
|
||||||
|
name: Public WC
|
||||||
|
size:
|
||||||
|
- 4.0
|
||||||
|
- 0.8
|
||||||
|
width:
|
||||||
|
- 1.5
|
||||||
|
- 0.3
|
||||||
|
proportion:
|
||||||
|
- 1.6
|
||||||
|
- 0.4
|
||||||
|
adjacency:
|
||||||
|
- c
|
||||||
|
count: 2
|
||||||
|
|
||||||
|
t10:
|
||||||
|
name: Staff WC
|
||||||
|
size:
|
||||||
|
- 3.0
|
||||||
|
- 0.6
|
||||||
|
width:
|
||||||
|
- 1.4
|
||||||
|
- 0.3
|
||||||
|
proportion:
|
||||||
|
- 1.6
|
||||||
|
- 0.4
|
||||||
|
adjacency:
|
||||||
|
- c
|
||||||
|
|
||||||
|
# Building constraints
|
||||||
|
storey_minimum: 1
|
||||||
|
storey_limit: 2
|
||||||
|
force_roof_garden: 0
|
||||||
|
|
||||||
|
ratio_circulation:
|
||||||
|
- 0.10
|
||||||
|
- 0.12
|
||||||
|
|
||||||
|
ratio_outside:
|
||||||
|
- 0.06
|
||||||
|
- 0.05
|
||||||
|
|
||||||
|
staircase_min: 1
|
||||||
|
staircase_max: 2
|
||||||
|
|
||||||
|
value_inside: 300.0
|
||||||
|
value_circulation: 50.0
|
||||||
|
value_outside: 100.0
|
||||||
|
value_supported: 300.0
|
||||||
47
experiments/run_9yx_sweep.sh
Executable file
47
experiments/run_9yx_sweep.sh
Executable file
|
|
@ -0,0 +1,47 @@
|
||||||
|
#!/usr/bin/env bash
|
||||||
|
# homemaker-py-9yx: non-synthetic third example (health-centre, 19 distinct
|
||||||
|
# codes / n=20 room instances, not a duplicated-count scale-up) repeats xyu's
|
||||||
|
# own protocol (DESIGN.md 31) -- ruin_recreate weight=3.0 ON vs OFF, budget
|
||||||
|
# 3000, 4 workers, finish-time collapse (default), N=15 seeds -- to see
|
||||||
|
# whether the ambiguous y51/xyu signal (9.3%->6.4% mean fails, p 0.098->0.059
|
||||||
|
# as N grew) was about room count or about the duplicated-code mechanism
|
||||||
|
# itself. Mirrors experiments/run_xyu_sweep.sh's run() function exactly,
|
||||||
|
# retargeted at examples/health-centre.
|
||||||
|
#
|
||||||
|
# Usage: experiments/run_9yx_sweep.sh
|
||||||
|
set -u
|
||||||
|
cd "$(dirname "$0")/.."
|
||||||
|
|
||||||
|
WORKERS=4
|
||||||
|
BUDGET=3000
|
||||||
|
SEEDS="1 2 3 4 5 6 7 8 9 10 11 12 13 14 15"
|
||||||
|
OUT=scratch/9yx_sweep; mkdir -p "$OUT"
|
||||||
|
TSV=scratch/9yx_sweep_results.tsv
|
||||||
|
[ -f "$TSV" ] || printf 'seed\truin\tbudget\tfails\tfitness\telapsed_s\n' > "$TSV"
|
||||||
|
|
||||||
|
run() { # seed ruin(0|1)
|
||||||
|
local seed="$1" rr="$2"
|
||||||
|
local tag="rr${rr}"
|
||||||
|
local dom="$OUT/${tag}_s${seed}.dom"
|
||||||
|
local log="$OUT/${tag}_s${seed}.log"
|
||||||
|
local flag="--no-ruin-recreate"; [ "$rr" = 1 ] && flag="--ruin-recreate"
|
||||||
|
echo ">>> seed=$seed ruin_recreate=$rr budget=$BUDGET"
|
||||||
|
local t0; t0=$(date +%s)
|
||||||
|
homemaker-evolve "examples/health-centre/init.dom" \
|
||||||
|
--budget "$BUDGET" --workers "$WORKERS" --seed "$seed" \
|
||||||
|
$flag --output "$dom" > "$log" 2>&1
|
||||||
|
local t1; t1=$(date +%s)
|
||||||
|
local fitness fails
|
||||||
|
fitness=$(sed -n 's/^best *: \([0-9.e+-]*\) .*/\1/p' "$log")
|
||||||
|
fails=$(sed -n 's/^best *: [0-9.e+-]* (\([0-9]*\) fails).*/\1/p' "$log")
|
||||||
|
( cd "examples/health-centre" && homemaker-fitness "$(realpath "../../$dom")" > /dev/null 2>&1 )
|
||||||
|
printf '%s\t%s\t%s\t%s\t%s\t%s\n' \
|
||||||
|
"$seed" "$rr" "$BUDGET" "${fails:-ERR}" "${fitness:-ERR}" "$((t1-t0))" >> "$TSV"
|
||||||
|
echo " -> ${fails:-ERR} fails, fitness=${fitness:-ERR}, $((t1-t0))s"
|
||||||
|
}
|
||||||
|
|
||||||
|
for seed in $SEEDS; do run "$seed" 0; done
|
||||||
|
for seed in $SEEDS; do run "$seed" 1; done
|
||||||
|
|
||||||
|
echo "=== 9yx health-centre N=15 sweep complete ==="
|
||||||
|
column -t -s $'\t' "$TSV"
|
||||||
Loading…
Add table
Reference in a new issue