What happens when a vector is fed into a value slot of the add node?

Question

I was wondering what happens when a vector is fed into a Math -> Add node. Notice that I'm asking about the Math -> Add node, not the Vector Math -> Add node.

My guess was that the node automatically works with the vector module, but I noticed that with different normal vectors the output is different.

Can somebody explain the behavior of the node in this case?

Answer 1

🟣 Vector values convert to ⚫ scalar values by averaging all three components, therefore the following material should be white:

(both branches compare as equal)

⚠ At very big values the $ε = 0$ starts to fail due to floating point inaccuracies:

(383 m cube)

Crantisz'es answer is incorrect, if it worked by converting 🟣 vector through 🟡 color to ⚫ scalar, then this material wouldn't be black (I even increased εpsilon to 0.1):

🟣 Vector is Converted to color (and vice-versa) by simply treating XYZ as RGB (I think it's fair to say it's reinterpretation, not conversion, the values in memory don't change), however, 🟣 vector and 🟡 color convert differently to ⚫ scalars:

• 🟣 vector to ⚫ scalar: $v = {1\over3} x + {1\over3} y + {1\over3} z = {x+y+z\over3}$
• 🟡 color to ⚫ scalar: $v = 0.2126r + 0.7152g + 0.0722b = $ luminance(rgb)

For completeness, ⚫ scalar converts both to 🟣 vector and 🟡 color by triplicating (repeating) its value on all 3 components, which maintains luminance, and so is a reverse operation for both $🟣➡⚫$ and 🟡➡⚫.

Geometry Nodes

In gnoodles the same rules apply, but additionally:

• All values convert to 🌸 boolean as False if they are $0$ (for vector all $xyz$ components must be zero; for color, RGB values must be $0$, but alpha doesn't matter)
• ⚫ floats convert to 🟢 integers by truncating, which is discarding the fractional part (rounding towards zero; flooring positive values and ceiling negative values).

Answer 2

Vector converts to color, and the color data is converted to its gray scale equivalent

From Blender Wiki:

Some socket types can be converted to other socket types either implicitly or explicitly. Implicit conversion can happen automatically without the need of a conversion node.

For example, color and float sockets can both be placed into one another. Once a socket conversion is made data may be lost and cannot be retrieved later down the node tree. Implicit socket conversion can sometimes change the data units as well. When plugging a Value input node into an angle socket will default to use radians regardless of the scene Units. This happens because the Value node has no unit while the angle input does.

Valid conversions:

Between color and vector – in this case the using individual color channels to store the vector.

Between color and float – the color data is converted to its gray scale equivalent.

Color/float/vector to Shader – implicitly converts to color and gives the result of using an Emission node.

Explicit conversion requires the use of a conversion node for example the Shader To RGB node or the RGB to BW Node node. The Math Node node also contains some functions to convert between degrees and radians.