🔱 Artha Math I2F

Artha Math I2F is the 🔱 Artha pack's integer→float converter: an INT in, a FLOAT out, plus a STRING version of the number for good measure. It's the mirror image of the pack's F2I node, and it exists for the same reason - ComfyUI's type system is picky, and every workflow eventually hits "this node wants a float and I only have an int."

It's a boring, three-line utility, and that's fine. The value here isn't the math - it's the type plumbing. Int→float conversions are lossless and free, so you'd be surprised how often this node is the invisible fix for a workflow that "just won't connect."

How it works

The integer input (INT, force-input so it's meant to be wired) gets cast with float(), producing float (FLOAT) - e.g. 3 becomes 3.0. The number output is the STRING form of that value ("3.0"). Two outputs, zero surprises.

Inputs that matter

• integer - the INT to convert.

Outputs: float (FLOAT) and number (STRING).

Installing it

One-pack install, same as all Artha nodes:

cd ComfyUI/custom_nodes
git clone https://github.com/Cyrostar/ComfyUI-Artha-Nodes
pip install -r ComfyUI/custom_nodes/ComfyUI-Artha-Nodes/requirements.txt

restart ComfyUI, or install "ComfyUI-Artha-Nodes" through ComfyUI Manager. No API key, no models - pure Python casting.

Common issues

• Nothing to wire in: the input is force-input by design. If you want to hand-set a value instead, use the pack's Math Integer node and feed it into this one.
• The STRING output shows 3.0, not 3: correct behavior - a float's text form includes the decimal. If you need "3" with no decimal, that's Math Integer's string output instead.
• Converting is pointless for you: true if your downstream node accepts INT fine. Use I2F only when a float input actually rejects an int connection.

The verdict: it's a two-output bridge node that does exactly what it says. Reach for it when an INT refuses to plug into a FLOAT socket, or when you want the textual form of an int alongside its float. Fifteen seconds of work, saves a workflow.