Is your feature request related to a problem? Please describe.
Visdom visualizes metrics well but has nothing for the hyperparameters that produced them. Users log configs into text windows or filenames and then eyeball which settings led to the best result. There is no way to see, in one place, how a knob relates to an outcome across many runs.
Describe the solution you'd like
A dedicated hyperparameter pane, fed by a vis.hparams() API that records a run's parameters and its final metrics. The pane should offer several linked views over the same data:
- Table : sortable, one row per run, params and metrics as columns.
- Parallel coordinates : one line per run across parameter axes, for spotting which regions of the space perform well.
- Scatter matrix (SPLOM) : pairwise parameter/metric relationships.
- Filters : narrow the run set by parameter range or value, with every view updating together.
Describe alternatives you've considered
- Pointing users at TensorBoard's HParams tab: means leaving Visdom and maintaining a second logging path.
- A plain table only: easy, but the whole value is in seeing relationships across many dimensions at once.
Additional context
Best built incrementally the logging API and pane shell first, then one view per PR, filters last so they can wire into all views at once. Handles missing values explicitly (runs with holes in their parameters) and shows a clear empty state rather than a blank canvas when nothing matches the current filters.
Is your feature request related to a problem? Please describe.
Visdom visualizes metrics well but has nothing for the hyperparameters that produced them. Users log configs into text windows or filenames and then eyeball which settings led to the best result. There is no way to see, in one place, how a knob relates to an outcome across many runs.
Describe the solution you'd like
A dedicated hyperparameter pane, fed by a vis.hparams() API that records a run's parameters and its final metrics. The pane should offer several linked views over the same data:
Describe alternatives you've considered
Additional context
Best built incrementally the logging API and pane shell first, then one view per PR, filters last so they can wire into all views at once. Handles missing values explicitly (runs with holes in their parameters) and shows a clear empty state rather than a blank canvas when nothing matches the current filters.