test(economy): measure start-field longevity instead of guessing (21.3, #87) - #115
Open
cubetribe wants to merge 1 commit into
Open
test(economy): measure start-field longevity instead of guessing (21.3, #87)#115cubetribe wants to merge 1 commit into
cubetribe wants to merge 1 commit into
Conversation
#87) The T-01 tester estimated the start reserve at 5.000 AE (it is 9.000) because nothing showed it. 21.2 fixed the visibility; this adds the missing design number: the REAL auto-cycle (2 AE/tick gather, 330-AE cargo, return tick per trip, footprint-reach deposit) runs on the canonical opening geometry — field (7,7), refinery (9,5) — until exhaustion: 1 harvester: 4.527 ticks = 7:33 min 2 harvesters: 2.263 ticks = 3:46 min 3 harvesters: 1.509 ticks = 2:31 min The gather rate dominates; travel vanishes under the D-104 footprint reach rule. Measured side finding: the opening supports at most ~3 walk-free harvesters per field — more need travel time (documented in the test). The reserve stays 9.000: the numbers support the D-102 expansion pressure instead of weakening it, and the T-01 misjudgement was a visibility problem (21.2), not an amount problem. The pins reopen the package automatically when any involved constant moves. No behaviour change, no baseline movement. Verified: dotnet test 730/730.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Was
Paket 21.3 aus Sprint 21 (#87): die Startmenge wird gemessen statt geraten. Neuer Test
tools/Nova.SimRunner.Tests/StartFieldLongevityTests.csfährt den echten Ernte-Auto-Zyklus (2 AE/Tick, 330 Laderaum, Footprint-Abkippreichweite D-104) auf der kanonischen Eröffnungsgeometrie — Feld (7,7) mit 9.000 AE, Raffinerie (9,5) — bis zur Erschöpfung und pinnt das Ergebnis:Skalierung ~1/N ist ebenfalls gepinnt.
Warum
Der T-01-Tester schätzte 5.000 AE (tatsächlich 9.000) — ein Sichtbarkeitsproblem, mit 21.2 gelöst. Die hier gemessenen Zahlen beantworten die eigentliche Designfrage („wie lange soll ein Startfeld tragen?"): solo gut ein Drittel der 20–35-min-Zielpartie (D-010), mit zwei Harvestern nur ~4 Minuten — genau der Expansionsdruck, den D-102 will.
Empfehlung (Inhaber-Veto vorbehalten): der Wert 9.000 bleibt. Kein Verhalten geändert, keine Baseline bewegt — die Pins öffnen das Paket automatisch wieder, falls sich eine der Konstanten je bewegt.
Mess-Nebenbefund: die Eröffnung trägt maximal ~3 lauffreie Harvester je Feld (Footprint-Reichweite der Raffinerie); mehr Harvester brauchen Wegzeit. Relevant für die Kartenarbeit in 21.6/21.7.
Nachweis
dotnet test tools/Nova.SimRunner.Tests -c Release: 730/730 grün (4 neue Tests)Betroffene Bereiche
tools/Nova.SimRunner.Tests/StartFieldLongevityTests.cs(neu),CHANGELOG.md(eine Zeile unter[Unreleased]→ Hinzugefügt).Merge-Hinweis: mögliche triviale CHANGELOG-Überschneidung mit dem 21.5-PR (beide Zeilen oben im selben Abschnitt) — Auflösung: beide behalten.