Allow `wandb.init` to set `wandb.run.dir`.

Problem or Use Case I am working with wandb and hydra. Like wandb, hydra creates a new output directory unique to each run. I would like to unite my wandb output directory and hydra output directory – for one, I would like to be able to save my hydra config.yaml to wandb.ai because it includes all of the parameters (including defaults) and not just the ones that were set from the command line.

Suggested Solution I think the best option would be to have separate dir and base_dir arguments for wandb.init.

[ethanabrooks]

I see. The symlink solution should work. Thank you.

[vanpelt]

Hey @ethanabrooks calling wandb.save on a file outside of the runs directory symlinks it into the run directory. Those paths are the sym-linked paths. If you look at the contents of config.yaml it should be hydra config.

I’m thinking there may be another problem however. We keep our own config.yaml file that may confuse our logic if its format changes. The most full proof way to save the config is simply to symlink or copy the file into the run directory as a different name.

os.symlink(os.path.abspath(".hydra/config.yaml"), os.path.join(wandb.run.dir, "hydra-config.yaml"))
wandb.save("hydra-config.yaml")