Remove custom W&B config changes

[siriuslee]

Removes custom 'algorithms' and 'models' sections from W&B

[ravi-mosaicml]

lgtm

[Averylamp]

lgtm, but also remove the custom flattening in the next 60 or so lines

[hanlint]

@siriuslee could you provide more motivation/context for this change, and how it impacts users of w&b?

[siriuslee]

@siriuslee could you provide more motivation/context for this change, and how it impacts users of w&b?

This removes some custom W&B work we did to make organizing our data collection efforts easier as the underlying composer library changed. A lot of these changes are now unnecessary or would be better made explicitly by the user. One of these changes (replacing model config data with the model name) actually deleted important configuration data.

As for the flattening, W&B will partially flatten the config dictionary that it's given for easier visualization and filtering runs. A nested key, after flattening, can be queried in W&B as "a.b.c". This doesn't work for objects that are lists, however, like schedulers. Our custom flattener takes care of that. After talking a bit more with @Averylamp , I've added a switch flatten_hparams that can optionally flatten the config before uploading if the user desires. I've defaulted it to False but am open to True if we think that is a more common use case.

[Averylamp]

lgtm thanks just make sure checks pass

[Averylamp]

@siriuslee could you provide more motivation/context for this change, and how it impacts users of w&b?

This removes some custom W&B work we did to make organizing our data collection efforts easier as the underlying composer library changed. A lot of these changes are now unnecessary or would be better made explicitly by the user. One of these changes (replacing model config data with the model name) actually deleted important configuration data.

As for the flattening, W&B will partially flatten the config dictionary that it's given for easier visualization and filtering runs. A nested key, after flattening, can be queried in W&B as "a.b.c". This doesn't work for objects that are lists, however, like schedulers. Our custom flattener takes care of that. After talking a bit more with @Averylamp , I've added a switch flatten_hparams that can optionally flatten the config before uploading if the user desires. I've defaulted it to False but am open to True if we think that is a more common use case.

This was a hack I introduced during data collection to make Niklas’ data querying more consistent