Ensure that AutoTuner makes metrics available in Tensorboard HPARAMS tab

[jeffng-or]

Subject

[Documentation] for documentation errors.

Describe the bug

Encountered an issue at customer site when viewing AutoTuner results in Tensorboard. The metrics die_area, effective_clk_period, and num_drc didn't appear in the Metrics section of the HPARAMS tab at the customer site, but they did appear on my GCP machine. Both Tensorboard sessions were being run using an Ubuntu-based docker container on a RHEL8 machine. The log files were identical on both machines.

Based on what I read online, this can happen based on the order that Tensorboard processes the files. My workaround was to run a recursive touch on all the log files to get a different order. Then it worked.

In terms of a more consistent solution, it seems like adding a SummaryWriter.add_hparams() call in the train function might work better.

Expected Behavior

Consistent display of the metrics in HPARAMS

Environment

I was using docker.io/openroad/orfs:v3.0-3276-g2813ba31f-verific

To Reproduce

Unable to repro within the PII GCP environment.

Relevant log output

Screenshots

No response

Additional Context

No response