Issue with sweeping variables in nested dictionary in config

Something seems wrong with nested parameters. The docs states, that dot is used to define nested variables in config.

This means that defining the following default config:

config = dict(
    my_dict = dict(inner_a = 'inner_a')
)

It should be possible to set inner_a to 'inner_a_from_sweep by the sweep:

method: random
metric:
  goal: minimize
  name: ""
parameters:
  my_dict.inner_a:
    distribution: categorical
    values:
    - inner_a_from_sweep
program: train.py

But running this:

config = dict(
    a = 'variable_a',
    my_dict = dict(inner_a = 'inner_a')
)

wandb.init(config=config)
config = wandb.config

print(config)

Outputs:

wandb_version: 1

_wandb:
  desc: null
  value:
    cli_version: 0.8.32
    code_path: code/../.local/bin/wandb
    is_jupyter_run: false
    is_kaggle_kernel: false
    python_version: 3.6.9
my_dict:
  desc: null
  value:
    inner_a: inner_a
my_dict.inner_a:
  desc: null
  value: inner_a_from_sweep

It seems like there is an issue with converting dot-variables back to dictionaries. I have fixed this myself by (though it is not very pretty and only works on one depth):

def fix_dict_in_config(wandb):
    config = dict(wandb.config)
    for k, v in config.copy().items():
        if '.' in k:
            new_key = k.split('.')[0]
            inner_key = k.split('.')[1]
            if new_key not in config.keys():
                config[new_key] = {}
            config[new_key].update({inner_key: v})
            del config[k]
    
    wandb.config = Config()
    for k, v in config.items():
        wandb.config[k] = v

[nate-wandb]

Hi all, thank you all for the feature request! Our engineering team has implemented the ability to sweep over values that are in nested configs and this will be available in release 0.12.17 when it is available.

Thank you, Nate

[tomaszpietruszka-globality]

@nate-wandb @sydholl the PR has been closed w/o merging - the functionality is still not there in 0.12.17 - or even RCs of 0.13.

Would you happen to have an ETA for a solution?