Allow for per-subset protected tags file#224
Merged
Merged
Conversation
Owner
|
@DraconicDragon thanks for implementing this, merging! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds the ability for the protected tags file code to use a protected tags file set on a per-subset basis with fallback to globally set prot tags file (eg through cli arg)
This is untested besides looking at the logs with debug_dataset and log_caption_tag_dropout set in the extra args of the UI and using multiple subsets with and without a protected tags file set - the logs seem to show that it works so in theory it should work I think; I'm just unsure with sd-scripts code if these logs are sufficient or not to determine if it works or not without having to (fully) train anything