question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Sweep configurations

See original GitHub issue

Hi I have two questions regarding sweeps:

1. Is it possible to re-configure a sweep?

Consider the following simple example:

  • I have a single hyperparameter - learning_rate.
  • I create the following sweep configuration YAML file (named wandb_conf.yaml):
program: main.py
method: grid
metric:
  name: val_acc
  goal: maximize
parameters:
  learning_rate:
    distribution: categorical
    values: [1e-5, 1e-4, 1e-3, 1e-2]
  • I create a new sweep using the following command: wandb sweep wandb_conf.yaml
  • New sweep is created with ID SWEEP_EXAMPLE_ID
  • I start the sweep by running wandb agent SWEEP_EXAMPLE_ID
  • After the agent runs several experiments, it’s obvious that setting learning_rate to 1e-2 is bad for the model

What I would like to do is:

  • Pause the sweep.
  • Update the sweep’s configuration by removing the value 1e-2 from the list of values of the learning_rate parameter:
parameters:
  learning_rate:
    distribution: categorical
    values: [1e-5, 1e-4, 1e-3]
  • Continue sweep

2. Is it possible to assign per-agent command line parameters? Let’s say that my program accepts the command line argument --gpus which sets the number of GPUs it uses. If I set this argument in the sweep’s YAML file, e.g.:

command:
      - "--gpus"
      - "4"

then, each agent that starts, will start an experiment using 4 GPUs.

This behavior is too strict. Let’s say I have two servers. Server A with 4 GPUs and server B with 8 GPUs. What I would like to be able to do is:

  • On server A: `wandb agent SWEEP_ID --gpus 4
  • On server B: `wandb agent SWEEP_ID --gpus 8

Issue Analytics

  • State:closed
  • Created 3 years ago
  • Comments:5

github_iconTop GitHub Comments

1reaction
issue-label-bot[bot]commented, Oct 24, 2020

Issue-Label Bot is automatically applying the label question to this issue, with a confidence of 0.61. Please mark this comment with 👍 or 👎 to give our bot feedback!

Links: app homepage, dashboard and code for this bot.

0reactions
sydhollcommented, Nov 18, 2021

In the past year we’ve majorly reworked the CLI and UI for Weights & Biases. We’re closing issues older than 6 months. Please comment to reopen.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Define sweep configuration - Documentation - Weights & Biases
Sweep configurations are nested; keys can have, as their values, further keys. The top-level keys are listed and briefly described below, and then...
Read more >
Configuration · GitBook
Use these configuration fields to customize your sweep. There are two ways to specify your configuration: YAML file: best for distributed sweeps.
Read more >
Sweep Settings
A sweep is a series of consecutive data point measurements taken over a specified sequence of stimulus values. You can make the following...
Read more >
Sweep configurations · Issue #1420 · wandb/wandb - GitHub
Hi I have two questions regarding sweeps: 1. Is it possible to re-configure a sweep? Consider the following simple example: I have a...
Read more >
Parametric Sweep (Job Configurations)
One of the main nodes is the Parametric Sweep ( ) job configuration, which can loop over a given set of parameters. For...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found