Immature Image Counter

Before a batch run, it helps to know how much you've already done. Immature Image Counter is a one-purpose node: it counts how many unique generated images exist in a given rapidfire output folder and hands you the number as an INT.

It pairs with the pack's CSV Writer and Immature Image Data Loader, which together form a "generate, log, review, re-enter" loop. The counter is the bit that answers "where am I in this batch?" - especially when you're re-queueing and want the workflow to decide what to do next based on how many runs have already happened.

How it works

The node looks in output/rapidfire/<date>/<subfolder>/ for .png files, then counts unique seeds by taking the seed prefix of each filename (everything before the first underscore). Two images with the same seed prefix count once - which matches the fact that one seed can produce multiple outputs in the pack's ecosystem. If the folder doesn't exist or the date is malformed, it returns 0 rather than crashing.

The date input defaults to today when left empty, and you can pin it to a past day with YYYY-MM-DD. The subfolder input (default "latent") lets you point it at a subdirectory of that day's output folder - handy if your workflow separates latent-stage outputs from finals.

One implementation detail worth knowing: the node declares IS_CHANGED as always-changing, so it re-executes and reports a fresh count on every run instead of caching the answer. That's what makes it usable as a live "progress so far" signal in a loop.

What you set

• date - leave blank for today, or YYYY-MM-DD for a specific day.
• subfolder - the subdirectory under that day's output/rapidfire folder to scan (default latent).

Output: file_count, an INT with the number of unique seeds found.

Install

It's part of comfyui-rapidfire with no extra dependencies. Get the pack via ComfyUI Manager (search "comfyui-rapidfire") or:

cd ComfyUI/custom_nodes
git clone https://github.com/Zeks/comfyui-rapidfire

then restart ComfyUI. If you're not running the pack's own output layout, this node has nothing to count - it's specific to the output/rapidfire/<date>/<subfolder> convention, so its usefulness is tied to using the family's save-and-reload loop.