EvaluateListMultiple6

Six-lane version of this pack's list-flavored Python evaluator: in1–in6 in, out1–out6 out, all of it list-typed, running your expression once per element across the whole set.

Where six list-lanes is actually the right size

By the time you're processing a batch and deriving six related values per item - say, from a list of source images: a width, a height, an aspect-ratio string, a resize target, a crop offset, and a formatted filename, all computed together per image - writing that as six separate single-lane EvaluateListMultiple1 nodes means repeating the per-item context six times. One EvaluateListMultiple6 node does it in a single expression with access to everything at once.

What "element-wise" means for six lanes

The node ships with its own hint pre-filled in the expression box (translated from the original Chinese): the expression is element-wise, and any output column that comes back None across every element in the batch gets dropped when results are merged. With six outputs in play, that matters more than it does at smaller sizes - it's easy to forget to assign one of six outN values inside a longer expression, and the node won't error on that, it'll just quietly drop the column.

Inputs and outputs

• expression (multiline STRING) - starts with the element-wise hint.
• input_count (INT, 1–20, default 6).
• print_to_console - per-element debug output.
• Optional: in1–in6 (type *).
• Outputs: out1–out6 (all is_list: true).

Same caution as the rest of the family

Unrestricted Python, no sandbox - the pack's own README describes this family as running "any fragment of Python code." At six lanes over a batch, a mistake in the expression multiplies across every element you're processing, so it's worth testing on a short list before pointing it at a large one.

Installing it

ComfyUI Manager: search RuiquNodes, install, restart. Manual:

cd ComfyUI/custom_nodes
git clone https://github.com/ruiqutech/ComfyUI-RuiquNodes

then restart.

Common issues

One or more output lists come back empty. Check that your expression actually assigns every outN it needs to for at least some elements - an all-None column gets silently skipped per the node's documented behavior.

The expression is hard to follow with six outputs. Comment which inN and outN correspond to what - with this many lanes in one text box, the graph itself won't remind you.

Something breaks partway through a long batch. print_to_console shows you what each element produced as it runs, which narrows down which item in the list is the actual problem far faster than reading the final merged output.

You don't actually have list data. If what you're feeding in is six plain scalar values rather than six lists, you want the non-list EvaluateMultiple6 instead - this node's element-wise merge behavior only does anything useful once there's a real batch running through it.