Spaces:
Runtime error
THIS APP IS MORE FUN ON THE A100 HARDWARE
That goes without being said but here are my findings:
- the compile time is zippy, it takes like a minute to deploy.
- best ranges for the parameters:
1-4 Guidance Scale (it is integer, floats offer no benefit)
3-100 iterations are suitable, mileage may very above 100 (outcomes at 500 were amusing seemed to repeat at higher settings).
8 images suitable for grid view, more than 8 is suitable for gallery view mode, 32 images is doable but resource intensive and can be dangerous if say you had 300 iterations and 32 images, it will take twenty minutes to see the outcome, and I'm talking A100 here.
For interactive use, use one image and higher ranges for seeds. I used seeds 1 to 100 as a slider than as a blank entry. Using a discrete set of seeds is suitable for reproducing results.
Things I'd like to see:
Image skipping. The seeds produce the same series of i ages, some valuable some not, it wouldbe nice to specify which images to render for higher iteration settings. Say I set it to generate 8 images, I'd like to have it evaluate the images enumerated by a fibonacci sequence (Resulting Image 1, 2, 3, 5, 8, 13, 21, 34, 55, 89), if I specified ten images.. So the 7th image would actually be the outcome if the input was set for the 21st image..
Other ideas, calling the app if public, with a REST url interface like how people share content socially, so that parameters could be set in the link and people wishing to reproduce the results would only need to click the link which would preconfigure the app to execute with the settings specified in the link..
For documentary purposes, if one wanted to elaborate on the purposes for each of the parameters and how they are used internally so that examples given with inoperable links could be salvaged by locating a cousin of the app or an app from another project.. (huggingface could benefit from this method of user outreach, as it would find interested parties through affiliates).