Since creating art with DD is an interactive, iterative, and time intensive process, it would be great to be able to automatically re-run the notebook with new changes after the current image is complete. Currently, that interactive process for batch runs is to wait until the image is complete and starts a new image in the batch, go to Runtime > Interrupt execution, make setup changes if you haven't already, scroll up above those changes and select a cell, and go to Runtime > Run after.
This could (possibly) be streamlined for multi-batch use with a checkbox in the "Do the Run!" section to restart_batch_with_updated_settings_when_complete. The workflow, while the batch is running, could be to make settings changes above and then check the checkbox. When the current batch image is complete, it could automatically restart the run at the "3. Settings" section to cover all changes before "4. Diffuse". Ideally the new checkbox would be programmatically unchecked so that the full n_batches could complete if the user is satisfied.
This way you would not need to closely monitor its progress—you could check on it, make small changes, and leave it.
Since creating art with DD is an interactive, iterative, and time intensive process, it would be great to be able to automatically re-run the notebook with new changes after the current image is complete. Currently, that interactive process for batch runs is to wait until the image is complete and starts a new image in the batch, go to Runtime > Interrupt execution, make setup changes if you haven't already, scroll up above those changes and select a cell, and go to Runtime > Run after.
This could (possibly) be streamlined for multi-batch use with a checkbox in the "Do the Run!" section to restart_batch_with_updated_settings_when_complete. The workflow, while the batch is running, could be to make settings changes above and then check the checkbox. When the current batch image is complete, it could automatically restart the run at the "3. Settings" section to cover all changes before "4. Diffuse". Ideally the new checkbox would be programmatically unchecked so that the full n_batches could complete if the user is satisfied.
This way you would not need to closely monitor its progress—you could check on it, make small changes, and leave it.