Nodes/Dream Project Animation Nodes/πŸ—Ž Int to Log Entry
ComfyUI Node

πŸ—Ž Int to Log Entry

The int-flavored logging brick β€” label a whole number and pass it down the chain

By alt-key-projectΒ·Created 3 years agoΒ·Updated 2 years agoΒ· 114
πŸ—Ž Int to Log Entry
    • log_entry
    β—„value0β–Ί
    β—„labelβ–Ί

    Int to Log Entry [Dream] is the integer twin of the pack's Float to Log Entry: it takes a whole number, attaches a label, and wraps it in a LOG_ENTRY for the Dream logging system. By itself it shows nothing - you need the pack's Log File node (or Log Entry Joiner) downstream to actually see the output. But for a long frame-by-frame render, "what was the frame count doing at minute 7?" is answered by nodes exactly like this one.

    It's a utility node from the Dream Project Animation Nodes pack (alt-key-project), the 2023 Deforum-style animation toolkit. Not actively maintained; nothing to maintain.

    What it does

    Inputs: value (INT) and label (STRING). Output: log_entry.

    The implementation is a single line - it builds a log entry containing label + ": " + str(value). No timestamps, no formatting, no persistence; the downstream nodes handle all of that. Its whole job is making an integer readable and transportable inside the logging chain.

    The shape of the logging system

    The pack's logging family has four pieces: the "X to Log Entry" nodes (Float, Int, String) create entries, Log Entry Joiner merges several entries into one (fewer wires), and Log File writes the result to disk. The pack's laboratory example chains Int and Float entries from the Laboratory node, joins them, and dumps a per-frame parameter snapshot to a file.

    Ints matter here because the animation's own bookkeeping is integer-typed: current frame, total frames, file counts. Logging frame: 412 next to a float like zoom: 1.03 gives you a timeline you can actually read back.

    Two habits that make it useful

    • Label everything. An unlabeled log entry is just a number on a line; the label is what makes the log greppable. "fps: 30" beats "30" every time.
    • Don't log every frame of everything. A 500-frame render logging five values per frame is 2,500 lines of noise. Log the ints that matter (progress, resets, one-time events) and use floats for the continuous stuff.

    Installing

    cd ComfyUI/custom_nodes
    git clone https://github.com/alt-key-project/comfyui-dream-project.git
    

    Or via ComfyUI Manager under "Dream Project Animation". No model downloads; the pack needs imageio, scipy, torchvision, pilgram, and evalidate, and pins numpy<2.0 (the usual NumPy-conflict suspect). Find it under Dream β†’ utils.

    Category✨ Dream/πŸ›  utils

    Inputs (2)

    NameTypeDefaultDescription
    valueINT0β€”
    labelSTRINGβ€”

    Outputs (1)

    NameTypeDescription
    log_entryLOG_ENTRYβ€”