Warnings are generated when the Valispace calculation algorithm detects possible issues with the current state of the formulas and values it is using. Their intention is to make you aware of these issues and provide a suggestion for fixing them.
Each warning has a 'code' for reference, which is a four-digit number. In general, the following high-level categories of warnings have been identified:
- 1000-1999: various warnings not belonging to other categories
- 2000-2999: calculation warning
- 2100-2199: unit conversion related warnings
- 3000-3999: requirements related warning
- 4000-4999: mode dependency and link matrix warnings
Warnings 2110 and 2120
Warnings 2110 and 2120 are created when unit conversion is enabled and units are specified that are not in the default unit list or in the custom defined units. See unit conversion for more on the unit conversion logic. They correspond to UndefinedUnitErrors in the Pint library.
Warning 2115 is created when an unsupported unit was entered (for example
%, -, $). This Vali will be treated as dimensionless, so the raw value will be used for any calculations. See unit conversion for the list of supported and unsupported units.
Warnings 2150 and 2160
Warnings 2150 and 2160 are created when unit conversion is enabled and the dimensionality of the units inside a formula does not match (for example you try to add meters to kilograms -> 2150 case) or the dimensionality of the formula result does not match with the unit of the Vali itself (for example you add two Valis in meter and the result Vali has a unit of kilogram -> 2160 case). See unit conversion for more on the unit conversion logic. They correspond to DimensionalityErrors in the Pint library.
Warnings 3100 and 3200
If the vali is outside the user defined requirements
Warnings 4000 4010
A 4010 warning is triggered when a formula of a Vali that is not mode dependent refers to a Vali that is mode dependent. This can in many cases lead to unexpected calculation results.
Example: mode dependent power consumption
In this example, the Fan component have a power consumption Vali that is a single value, whereas its children components Motor and speed_controller have powerConsumption matrices that are mode-dependent. The Fan power consumption has a standard sum of children formula.However, which mode of its children should it account for?
The recommended way to fix this is to make the Fan power consumption mode dependent. The 'modes' page explains how to do this. Then a link can be made between the Fan and its children modes