Website: machine estimator v3 — the bar shows what the box's memory is used for (still unlisted, R-997)
gates / gates (push) Successful in 6m29s
gates / gates (push) Successful in 6m29s
The bar keeps its length (the fits-well box memory) and is split into base system (box - guest), Felhom's own services, each app's peak (largest first, the dashboard's palette minus amber and its first blue; beyond 8 apps one group) and spare room (guest - peak) — all from the one rule; a test proves the parts sum to the bar within 1 MB. A legend under it (not sticky) and one sentence explain the recommended size. Typical figure moved into the method fold-out. English: 'an 8 GB machine'.
This commit is contained in:
@@ -1,3 +1,12 @@
|
||||
## 2026-10-13 (evening) — estimator v3: segments and the English article under test
|
||||
|
||||
- `build_sizing_web.py`: `bar_app_colours` (8) in the data file, so the script holds no number of its own.
|
||||
- `test_build_sizing_web.py` (10 tests): the bar's segments (base system = box − guest, Felhom, each app's peak,
|
||||
spare = guest − peak) add up to the bar within 1 MB for the four cases and for nothing selected; base and spare are
|
||||
never negative; the household preset by hand (spare = 5,515 × 0.5, base = 4,096 + 612); every English
|
||||
recommendation gets „an 8" / „a 12" … Red-proofed: the „an 8" rule removed, the JS computing spare from the typical
|
||||
figure, and segments off by 50 MB each convicted.
|
||||
|
||||
## 2026-10-13 (afternoon) — estimator v2: `build_sizing_web.py` box sizes, tests for the inverse
|
||||
|
||||
- `build_sizing_web.py`: `boxes_gb` = 8, 12, 16, 24, 32, 48, 64; new `bar_marks_gb` and `bar_max_gb`.
|
||||
|
||||
Reference in New Issue
Block a user