Optimization Paths
Filesystem-path conventions for optimization runs.
Lays out a stable directory shape under any host application's workspace:
<appWorkspace>/
output/
<sanitizedAnalysisName>/ ← analysis output directory
run-001/ ← one run-NNN per submit
summary.toml
iteration_history.csv
…
<trace>.csv ← when tracking enabled
run-002/
…Content copied to clipboard
These helpers are pure functions over Path / SolverSpec / SolverTrackingSpec — no Swing dependency, no live engine state. Any host application that wants to honour the standard layout (so users can navigate between runs in a file manager with stable expectations) calls these.
Substrate-level API — usable by any UI shell.
Functions
Link copied to clipboard
Default CSV-trace file stem when the user hasn't set one. Format: <solverName>_trace when the solver has a name; <kindLabel>_trace otherwise.
Link copied to clipboard
Find the next unused run-NNN subdirectory under analysisDir.
Link copied to clipboard
fun traceFilePath(runOutputDir: Path, trackingSpec: SolverTrackingSpec, solverSpec: SolverSpec?): Path?
Compute the CSV trace file path inside a specific run directory.