raf

> Kohya is suggesting to move the config from wandb to the accelerator interface via init_kwargs/config as starting the wandb init outside the accelerator hook could cause side effects. >...

> Kohya is suggesting to move the config from wandb to the accelerator interface via init_kwargs/config as starting the wandb init outside the accelerator hook could cause side effects. >...

No longer necessary m. It sheen incorporated to gui a few releases back

Sorry, it has been committed on v23.0.12 Support for Wandb project and run name has been added to the gui Best thanks best regards, raf On Mon, 1 Apr 2024...

> above the `accelerator.init_trackers` call: you're absolutely right. Hadnt noticed the parameters were not being sent

> I'm on the latest kohya_ss version, and training parameters are not sent to wandb without my changes. I don't care much about just the run name. > > Also...

> Not by default, you need to make a config for it afaict (of which I've seen no examples). > > My PR makes it so if `log_tracker_config` isn't specified,...

is it possible to use bothM init_kwargs["wandb"] = {"config": args} in sdxl_train.py and WANDB run name for model name Log tracker name for project name So as to take advantage...

in sdxd_train.py do i remove the line: init_kwargs = toml.load(args.log_tracker_config) and add instead: init_kwargs["wandb"] = {"config": args} [image: image.png] ? On Mon, Apr 1, 2024 at 6:07 AM Nick Renieris...

> see my PR: https://github.com/kohya-ss/sd-scripts/pull/1231/files#diff-62cf7de156b588b9acd7af26941d7bb189368221946c8b5e63f69df5cda56f39R705-R707 > > then: `log_tracker_name` -> wandb project name `wandb_run_name` -> wandb run name don't specify `log_tracker_config` awesome that's working now, thanksalthough, there seems to be...