13 docs tagged with "runs"

Set unique tags with wandb.init(tags='your_tag'). This allows efficient filtering of project runs by selecting the corresponding tag in a Project Page's Runs Table.

Yes, you can also use tags or custom metadata to categorize runs. That can be done using the Group button which is available in the Workspace and Runs views of the project.

If a grid search completes but some W&B Runs need re-execution due to crashes, delete the specific W&B Runs to re-run. Then, select the Resume button on the sweep control page. Start new W&B Sweep agents using the new Sweep ID.

A run can have multiple tags, so grouping by tags is not supported. Add a value to the config object for these runs and group by this config value instead. This can be accomplished using the API.

Changing the colors of individual runs within a group is not possible. All runs in the same group share a common color.

Using wandb.log({'finalaccuracy' }) updates wandb.settings['final_accuracy'], which reflects the value in the runs table.

There are several ways to manage experiments.

To recover deleted runs, complete the following steps:

To launch automated tests or internal tools that log to W&B, create a Service Account on the team settings page. This action allows the use of a service API key for automated jobs, including those running through continuous integration. To attribute service account jobs to a specific user, set the WANDBUSERNAME or WANDBUSER_EMAIL environment variables.

To resolve permission errors when logging a run to a W&B entity, follow these steps:

Limit each project to approximately 10,000 runs for optimal performance.

You can change the group assigned to a completed run using the API. This feature does not appear in the web UI. Use the following code to update the group:

You can move a run from one project to another by following these steps: