invoke-ai / invoke-ai/InvokeAI
[enhancement]: Options to control deletion or movemet of Safetensors when converting to diffusers
- Dominant language
- Python
- Stars
- 28.2k
- Forks
- 3k
- Avg merge
- 6d 5h
- Merged PRs (30d)
- 19
Description
### Is there an existing issue for this?
- [X] I have searched the existing issues
### What should this feature add?
Currently, if the safetensor is in the invoke internal directory, it is deleted, and not if elsewhere. Also, the options are only to put the converted diffuser in the invoke directory, or to manually type in another location.
- Please add an option to convert in the same folder where the safetensor currently is, rather than having to type in the location as "custom" each time. This would be faster and allow for easier serial conversion of large numbers of safetensors.
- Rather than based on the file location, ask the user if they want the safetensor to be deleted or not. An added option could be to designate a location to move the safetensor to after conversion.
- Please add file browsers to allow the user to more easily find and set the place they want things to go, if not the default or the same location as current.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by locating the safetensors-to-diffusers conversion flow and the existing controls for output location and source-file deletion. Done means users can choose the source folder, decide whether to delete or move the safetensors file, and use file browsers instead of manually entering custom paths.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- ai
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100