Should walk instead be a pipeline?

[nateraw]

When I first made this repo, it was basically just a script, which is why the stable_diffusion_walk.py file is the way it is. However, as the ideas and features here grow, it may be nice to structure things a bit better (especially if we add new workflows like #27 and #26 ).

We could have logic of walk be the __call__ function of a new pipeline, StableDiffusionForVideosPipeline or whatever. This would be a self-contained pipeline object - essentially building on top of the existing pipeline file. Then, as we write up the logic for the above additional workflows, they can become their own self-contained pipelines as well.

Anybody have any thoughts here? This would be a pretty big restructure with breaking API changes, but would be a bit more "professional" and less hacky. But maybe its fine this remains hacky. idk😅

[nateraw]

I realize how gross it is to have a module in a python package initialize a torch model in the global scope haha.

[nateraw]

its a pipeline now