Raw, Evaluated, and Resolved Values

Three stages of a value

Every input moves through three stages:

• 1. Raw - what you enter (literal or expression)
• 2. Evaluated - the result of executing that input
• 3. Resolved - the final value the system actually uses

Resolved is always the value used by the system. If evaluation succeeds: Resolved = Evaluated If evaluation fails: Resolved = Default (fallback)

Raw -> Evaluated -> Resolved (always used)

Resolved only differs from evaluated when evaluation fails.

When evaluated differs from resolved

Resolved only differs from evaluated when evaluation fails, such as:

• Type mismatch
• Invalid formula
• Missing dependency
• Value outside allowed constraints

In these cases, the system uses the default fallback value.

Example

You enter: Control Load = {expression}

• Case 1 - valid: Evaluated = 1200
• Case 1 - valid: Resolved = 1200
• Case 2 - invalid: Evaluated = error
• Case 2 - invalid: Resolved = 750 (default fallback)

The system always continues using RESOLVED.

Where you see each stage

• Raw -> shown in the input field
• Evaluated -> computed internally
• Resolved -> shown under 'RESOLVED'

The RESOLVED field shows the actual value used by the system.

Try it

See how valid and invalid values affect RESOLVED.

1. Enter a valid value -> RESOLVED matches evaluated
2. Enter an invalid expression -> RESOLVED uses default
3. Open Outputs -> Data to compare behavior

Focus on RESOLVED - this is what the system actually uses.

What happens during evaluation

• Raw is evaluated first
• If evaluation succeeds -> evaluated becomes resolved
• If evaluation fails -> resolved falls back to default
• All geometry, logic, states, and outputs use RESOLVED values.

Key idea

The system always runs on RESOLVED values.