Outputs

Argonaut outputs a results screen, downloadable files, logs, and visualizations. The exact files depend on the selected algorithm.

Tree-Based Files

Tree-Based Iterative produced the following downloadable files in the tested run.

File	Contents
`global-cost.csv`	Iteration trace of global cost with `Iteration`, `Mean`, `Stdev`, and one column per run.
`unfairness.csv`	Iteration trace of unfairness.
`local-cost.csv`	Iteration trace of local cost.
`global-complex-cost.csv`	Iteration trace of the weighted total cost.
`selected-plans.csv`	Selected plan index for every agent at every iteration.
`indexes-histogram.csv`	Distribution of selected plan indexes.
`termination.csv`	Terminal iteration for each run.

Example selected-plans.csv header:

Run,Iteration,agent-0,agent-1,agent-2

Example termination.csv:

Run,Terminal Iteration
0,1

Tree-Based Logs

The Tree-Based Logs tab shows the Java optimization backend configuration and runtime messages. It includes dataset, output path, number of simulations, number of agents, number of plans, plan dimensions, iterations, children per node, objective weights, cost functions, loggers, and runtime.

Brute Force Files

Brute Force produced the following downloadable files in the tested run.

File	Contents
`solutionwiseresults.csv`	Every collective solution tuple with global cost and local cost.
`epossimulationresults.csv`	Start tuple, final tuple, final global/local cost, and whether the run hit the global optimum.
`summary.json`	Summary values including total combinations, best costs, best tuple, mean global cost, min/max local cost, agent count, and success rate.

Brute Force Logs

The Brute Force Logs tab shows the input file, agent count, plan count per agent, dimension count, total solution count, brute force runtime, global optimum, EPOS-from-all-starting-positions runtime, success rate, output folder, and generated radial visualization files.

Combined Mode Outputs

Both mode displays two output sections:

Tree-Based (I-EPOS) Results with the Tree-Based files and logs.
Brute Force Results with the Brute Force files and logs.

In the tested deployment, the combined Logs tabs showed the I-EPOS log followed by a BRUTE FORCE LOGS section. The second Logs tab showed the same combined log content again.