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

πŸ—Ž Float to Log Entry

Label a number, pass it on β€” the building block for the Dream logging system

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

    This is a boring node, and it knows it. Float to Log Entry [Dream] takes a float, slaps a label on it, and hands you a LOG_ENTRY - the pack's little logging data type. On its own it does nothing visible. Wired into the pack's Log File node (or joined with other entries via Log Entry Joiner), it's how you record what your curves and calculations are doing at every frame of a long render.

    It's part of the Dream Project Animation Nodes pack (alt-key-project), the 2023 Deforum-style animation toolkit. Unmaintained since the author pivoted to comfyui-dream-video-batches, but logging primitives don't rot.

    What it does

    Two inputs: value (a FLOAT) and label (a STRING). Output is a single log_entry.

    The mechanism is exactly one line in the source: it creates a log entry containing label + ": " + str(value). No formatting, no timestamp, no persistence - that's the job of the other nodes in the logging chain. This node's only responsibility is wrapping a number so the rest of the system can carry it around.

    Where it fits: the pack's logging family is Float/Int/String to Log Entry (the input side), Log Entry Joiner (merges several into one), and Log File (writes to disk). The pack's laboratory example workflow chains a bunch of these - you label "zoom", "noise", "brightness" values from the Laboratory node, join them, and dump them to a log file so you can see the whole parameter set at each frame.

    When you'd actually wire it in

    Debugging, mostly. When an animation looks wrong and you suspect it's a parameter drifting, route the suspect value here, join it with the frame counter info, and log it. Two useful habits:

    • Give every entry a label - the whole point is that elapsed_seconds: 12.3 is readable in a log file and a raw 12.3 is not.
    • Keep the logging chain short. A Log File node at the end of a 500-frame render can get big fast; log the values you need, not everything.

    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, evalidate - and it pins numpy<2.0, which is the thing to check if you get NumPy errors. Find it under Dream β†’ utils.

    Category✨ Dream/πŸ›  utils

    Inputs (2)

    NameTypeDefaultDescription
    valueFLOAT0.00β€”
    labelSTRINGβ€”

    Outputs (1)

    NameTypeDescription
    log_entryLOG_ENTRYβ€”