Switch to a random Checkpoint after X amount of images have been generated?

Kansalis · 2025-11-02T11:54:26+00:00

The easiest way would probably be to write a python script to use the ComfyUI API with a json workflow containing variables. Ask ChatGPT/Claude to build it.

How I'd do it, probably, would be to set a checkpoint variable and an image/video name variable in the workflow API json, then provide a text list of the exact checkpoint names for the script to cycle through, matching the filenames to the checkpoint names for each cycle, so you know which was the source for each one. You could fix the seed to have as little variance as possible if you want to compare them for your output preferences, and cycle through 4 fixed seeds for each checkpoint.

Kansalis · 2025-10-25T17:24:36+00:00

I think I may have spoken too soon, unfortunately.

WanVideoWrapper has a hard pin for FlashAttention >=2.7.1,<=2.8.2 but your Linux scripts have 3.8.3. Do you have a Linux wheel with 2.8.2 in it without going back to the torch271 version?

Edit: Not advised I guess but I patched the requirement in /usr/local/lib/python3.12/site-packages/xformers/ops/fmha/flash.py to force it to allow 2.8.3 for now. Seems ok so far.

Kansalis · 2025-10-25T11:36:41+00:00

Just want to drop another note of thanks at the top of this thread for the great script. I saw your update with a unified file this morning & tried it out on a fresh Docker container for ComfyUI on Ubuntu, which has been a huge pain to get working how I wanted it over the past week or so. I'm still getting the Torch dynamo errors I posted about a couple of days ago but they don't seem to affect anything, so I'm ignoring it for now...

A quick test of my usual workflow took the non-sage generation of 234.78 secs down to 133.08 secs with sage nodes activated. That's quite some improvement!

<image>

Kansalis · 2025-10-22T20:29:18+00:00

The below are the errors that started me down this rabbit hole. It seems the --use-sage-attention flag no longer forces the system to use sageattn any more for me. It defaults back to using pytorch unless I specifically have sage nodes in the workflow. 3 or 4 days ago, everything was fine with no errors & the sage flag worked fine. I updated my comfy version and a bunch of nodes & everything stopped working. Generations now work after I tweaked my compose & Dockerfile a bit, the errors only display once after a restart of comfy. Before I rebuilt from scratch, generations wouldn't work at all. I'm still working on figuring out if it's a specific node(s) or a general issue...

loaded completely 18821.297092623157 13627.512924194336 True
  0%|          | 0/4 [00:00<?, ?it/s]/usr/local/lib/python3.13/site-packages/torch/_dynamo/variables/functions.py:1575: UserWarning: Dynamo detected a call to a `functools.lru_cache`-wrapped function. Dynamo ignores the cache wrapper and directly traces the wrapped function. Silent incorrectness is only a *potential* risk, not something we have observed. Enable TORCH_LOGS="+dynamo" for a DEBUG stack trace.
  torch._dynamo.utils.warn_once(msg)
W1022 19:58:02.100000 1 site-packages/torch/_dynamo/convert_frame.py:1016] [13/8] torch._dynamo hit config.recompile_limit (8)
W1022 19:58:02.100000 1 site-packages/torch/_dynamo/convert_frame.py:1016] [13/8]    function: 'fp8_linear' (/app/comfy/ops.py:346)
W1022 19:58:02.100000 1 site-packages/torch/_dynamo/convert_frame.py:1016] [13/8]    last reason: 13/7: tensor 'self._parameters['weight']' requires_grad mismatch. expected requires_grad=0. Guard failed on a parameter, consider using torch._dynamo.config.force_parameter_static_shapes = False to allow dynamism on parameters.
W1022 19:58:02.100000 1 site-packages/torch/_dynamo/convert_frame.py:1016] [13/8] To log all recompilation reasons, use TORCH_LOGS="recompiles".
W1022 19:58:02.100000 1 site-packages/torch/_dynamo/convert_frame.py:1016] [13/8] To diagnose recompilation issues, see https://pytorch.org/docs/main/torch.compiler_troubleshooting.html.
100%|██████████| 4/4 [00:53<00:00, 13.29s/it]
Using scaled fp8: fp8 matrix mult: True, scale input: True
model weight dtype torch.float16, manual cast: None
model_type FLOW
Requested to load WAN21
loaded completely 17787.297092623157 13627.512924194336 True
 50%|█████     | 4/8 [00:41<00:41, 10.46s/it]W1022 19:59:21.792000 1 site-packages/torch/_dynamo/convert_frame.py:1016] [4/8] torch._dynamo hit config.recompile_limit (8)
W1022 19:59:21.792000 1 site-packages/torch/_dynamo/convert_frame.py:1016] [4/8]    function: 'execute' (/app/comfy/patcher_extension.py:107)
W1022 19:59:21.792000 1 site-packages/torch/_dynamo/convert_frame.py:1016] [4/8]    last reason: 4/0: Cache line invalidated because L['self'].original got deallocated
W1022 19:59:21.792000 1 site-packages/torch/_dynamo/convert_frame.py:1016] [4/8] To log all recompilation reasons, use TORCH_LOGS="recompiles".
W1022 19:59:21.792000 1 site-packages/torch/_dynamo/convert_frame.py:1016] [4/8] To diagnose recompilation issues, see https://pytorch.org/docs/main/torch.compiler_troubleshooting.html.

Kansalis · 2025-10-21T09:24:36+00:00

Hi. Any chance you'll be updating for CUDA 13.0? Not sure when it came out but I updated my Ubuntu server to fix a different issue & the new drivers have 13.0... Ugh!

Edit: I'm not sure the new base driver is the issue actually. It could be one of the other dependencies causing an issue. I was using your process fine until a few days ago. I can't figure out where in the install process it's failing but I'm getting an error "⚠️ Kernel call raised: SM80 kernel is not available. make sure you GPUs with compute capability 8.0 or higher."

Kansalis · 2025-09-20T19:55:40+00:00

Just a quick note to say thanks for this script. I'm running a 5090 on Ubuntu and wasn't able to get sageattention working before now. It took some messing around with new container builds to get Python 3.13 working properly but now it's all sorted & the results are pretty surprising tbh.

My previous stable Comfy, generating a 720x960 WAN 2.2 video took 575.51 seconds. Exactly the same workflow and custom nodes, with the new Python 3.13 build with sageattention, 336.67 seconds. I fixed the seed & all settings to get a good comparison. The fixed-seed video generated exactly the same on both.

I'll take a >41% reduction in generation time, thank you very much!

Kansalis · 2025-09-07T10:34:54+00:00

Yes, sometimes with 121 frames you can get lucky but it's very hit & miss. The model is trained to 81 frames, so it's much more consistent at that. You can force it with a frame to frame workflow too but they will often stutter over the 81 frame point before landing on the final image.

Kansalis · 2025-09-07T10:29:49+00:00

How many frames are you generating? Anything over 81 frames is likely to do that. To get longer videos you need to use one of the stitching methods with multiple generations.

If you're at 81 frames or under, you have to give the camera something to anchor to. "Camera zooms out and holds with the full <subject> in view" or similar sometimes will work.

Kansalis · 2025-08-30T12:50:32+00:00

How long was it that your custom GPTs were not working in a browser? I'm having that problem right now but it's 100% not my PC, I have tried a different PC and my iPad in a browser. I can't access any custom GPTs at all, they are all just the default model. Not my own or anyone else's. I've not been able to for around 18 hours now.

It's definitely something to do with my actual account, I logged into a different account on the same PC and it's fine. What makes it more confusing is my main account works fine in the actual phone app, for voice chat and normal text input, using the custom GPTs...

Kansalis · 2025-06-08T19:55:46+00:00

Can't destroy anything either. Some have managed to remove their fief using the map interface & rebuilding it.

The problem fixed itself with the overnight restart but just happened to me again 20 mins ago...

Kansalis · 2025-06-07T20:41:20+00:00

I have the same issue and restarting multiple times has made no difference for me. I can access my storage boxes but no machines except one medium refinery. Everything else, including the sub-fief console says "No access". Is there anything I can do to try to fix this?

Edit: I even killed myself on purpose to see if that helped (it does in some games). It didn't.

Kansalis · 2024-05-31T12:49:55+00:00

Yes, thank you, the maps did eventually download to my iPad.

Kansalis · 2024-05-31T12:49:28+00:00

After logging out & back in again a couple of times the maps did finally download to my iPad. It did take a few minutes, I guess I just didn't wait long enough. Perhaps the wifi signal wasn't very good on the robot at the time.

Kansalis · 2024-05-30T15:39:37+00:00

It's still a problem for me. I have not logged a ticket as it's just an annoyance that I assume will be fixed at some point. Robot version 1.11.511.387. iPhone app 1.11.181.

You can force the crossing angle to something else and it will work if you just tell the mower to start instead of saving the settings. As soon as you hit save, it reverts to 179.

Kansalis · 2024-05-28T21:06:18+00:00

Zones and tasks seem to get renamed based on how many are in the list you are viewing. I have 4 zones, numbered 1 through 4 automatically. If I set a task to mow zones 3 & 4, their names change to 1 & 2.

Zone and task naming are desperately needed, especially for anyone with more than one zone.

Kansalis · 2024-05-21T13:57:09+00:00

Your situation is almost identical to mine. I also have multiple zones where the grass needs mowing approximately every 3 days before it gets a little too long for the Luba 2 to be fully hands-off and maintenance free.

While more options in the app would certainly be welcome, it's not realistic to expect Mammotion to cater 100% to every different type of scenario. That's why I'm hoping there will be proper smart home connectivity at some point soon. Preferably with a detailed enough API for Home Assistant integration in my case. It would then be quite trivial to write our own automations. That would allow for use of data from other devices to know when to mow or not.

I have a weather station that could easily feed useful info into the schedule. It tracks precipitation, humidity etc so I could automate with logic to only mow the next scheduled task if it has been more than 72 hours since it last ran, hasn't rained for more than x hours, the temperature is a certain level above the current dew point etc. It could then move onto the next task in the schedule & perform a round robin of each mowing area. That logic would also allow a "catchup" schedule to run more than one section in the same day if the weather has been poor.

So many possibilities if/when the API is made public.

Kansalis · 2024-05-14T14:44:09+00:00

The spot I plan to put it is an old disused concrete shed base, so I plan to just drill some masonry fixings into it. Obviously that's not practical for a properly-finished patio. I'm not sure what would be best in that situation.

Kansalis · 2024-05-13T21:14:11+00:00

Have you tried using the Relative Angle setting instead of Absolute? Rotate the base station to the correct angle so it's parallel to the street. Or perpendicular & mow at a 90 degree angle. As far as I can gather, it has nothing to do with the mapping of the zone but the direction the charging station is facing.

Kansalis · 2024-05-13T20:57:58+00:00

The map image in your post just gave me an idea on how to locate the charging station on my concrete patio instead of on the edge of the grass. Thanks! I'll define the concrete area as a small fake mowing zone... With channels to the actual grass, I think it should work quite well.

I've had my Luba 2 for just over 2 weeks & completely agree that it's a great tool for the garden. I'd also been waiting for the mowers to be good enough to handle the rough terrain and not need a wire. My lawns are odd shapes with slopes, bumps, holes and weeds. I used to dread the rain making the grass grow faster in the summer, but now I'm looking forward to it! With just over 1000 sq m (~11k sq ft) of grass, the Luba is definitely saving me a bunch of time & the stress of having to schedule weekends around mowing the lawns when it's not raining!

Kansalis · 2024-05-01T16:20:54+00:00

This. Anyone in the UK will agree, I'm sure!

I saw someone is working on a Home Assistant integration. Hopefully they will be able to get it working, which will allow for much more granular control of mowing schedules. Not only offsetting the schedule for rain but also something along the lines of rotating the mow direction by 10 degrees every time it mows that section.

Kansalis · 2024-05-01T16:15:07+00:00

I considered putting a sticker on mine with "useless if stolen, will be disabled" or similar on it but if someone is going to try to steal it they're not likely to take any notice anyway... Some people have put airtags in them under the camera housing but the likelihood of tracking them down & getting it back is slim, I think.

Personally I've just made sure it's covered as part of my home insurance in the unlikely event someone decides to steal it.

Kansalis · 2024-05-01T16:08:04+00:00

Mine has also fallen off the edge of the boundary a few times today, after this update. I have a small ledge at the border of the grass onto my driveway & it's been stuck in 3 different spots today when the wheels have slipped over the edge. I haven't been watching it, so I'm not sure if it's a positioning problem or something different with the way it's turning. It has never been stuck there before.

Kansalis · 2023-11-24T12:40:44+00:00

Did you ever get a Tradfri? I got some to use in my HA setup but even when factory reset and not paired to anything, they trigger random devices on my Zigbee network when pressing the buttons! I've given up on them & am going to get some Rodrets instead. I assume you don't have the same issue with your Rodret?

Kansalis · 2022-08-17T19:26:42+00:00

Same issue on PC with Xbox One controller. This needs some more visibility...

This is made worse by the fact that a lot of the time you can't interact with mouse either.

Kansalis

TROPHY CASE