August 11, 2026 — optimize on Generate, clearer inputs, calculation walkthrough
- Optimize storage runs on Generate by default. After the baseline is built, Generate may replace it with the lowest-total-storage candidate that meets a 10% local-gap target under 0% extra storage, with density capped by
largest_run_time_fractionand repeats floored attotal_time_short / tau_alpha. If nothing qualifies, the baseline is kept. Compact limits sit under “Not recommended to change”; Compare remains for manual exploration.reproduction.txtrecords the limits and outcome. - Required parameters and defaults match how people actually set a run. Order is
dt1 → dt2 → tau_alpha → tau_equil → totals; filenames are Advanced.dt1anddt2/dthave no numeric defaults (dt2may be blank for long-only aging).tau_equildefaults to50*tau_alpha, short production to150*tau_alpha, andfirst_run_time_longto20*dt1(typical thermostat settle scale). Units are labeled in LJ time; help text marks first-run fields as dynamic range andlargest_run_time_fractionas information resolution. Long-only aging (total_time_short_sequence = 0) hides short filenames and optimize, but keeps the short-cycle template controls so the long sequence can still be sized. - Printed schedules agree with geo-rev11 on LJ→timestep ties. Half-integer step counts use Python 3 / geo-rev11 half-even rounding so the site’s short cycle matches the printed command.
- How was this schedule calculated? After Generate, a collapsed walkthrough under Summary explains this run’s short dump count, long-sequence gap match, typed vs default values, and whether optimize changed the baseline—without restating the
?help or command-flag essays. - Geometric-runtime generator is the site root. The older geometric dump-time app (
--old) is archived underdeprecated/. - Exported schedule text uses Unix newlines (LF). ZIP schedule files and snippet text are assembled with LF line endings, not CRLF.