Tunny Icon
TunnyDocs

The next-gen Grasshopper optimization tool.

Startup CLI

Startup options

Launch Tunny Dashboard from a terminal or another tool:

TunnyDashboard.exe -i study.log -a ./artifacts
Option Value Purpose
-i, --input Result path or connection URL Open an optimization result source at startup.
-a, --artifact Existing directory Set the default artifact root directory for this session.

Both options are optional and may appear in either order. The result source and artifact root are independent: the directory need not be next to the result file, and it is a directory, not an individual artifact file. You can also launch with only --artifact and open results later through the GUI.

Relative paths are interpreted from the working directory where the application is launched. An artifact directory must already exist at startup. A nonexistent path or an individual file causes a CLI error and aborts startup. Missing or duplicate artifact arguments also cause a CLI error.

Session behavior

The CLI artifact root remains available when you open another result source, switch studies, or reload results. A directory explicitly selected through the GUI Artifacts control takes priority over the CLI default and remains the session root through those changes. Without --artifact, existing artifact resolution is unchanged unless you explicitly select a directory in the GUI.

DesignExplorer-format CSV images

DesignExplorer-format CSV is the DesignExplorer application's output format targeted by the parser: one trial per row, with in:<name> parameter columns, out:<name> objective columns, and an optional img column of relative artifact paths.

With an explicit artifact root (CLI or GUI), img paths resolve relative to that root while retaining their association with each trial. Without an explicit root, they resolve relative to the CSV file's parent directory. Only existing files with safe relative paths are included; absolute paths and parent-directory (..) references are excluded. The resolved file must also remain inside the effective root directory: a symbolic link that resolves outside it is excluded, even if the img path itself looks like a safe relative path.