Alerts

Alerts are informational messages that are produced as you change the values of your design.

Alert panel

Press Alert buttons on the main pages (Advanced and Calculator Views) to see an alert presentation that is organized by severity:

Severity	Content	Font
Err	value is outside its valid range	Bold
Warn	relationship between values incorrect or invalid	Bold, Italic
Notice	constraints that are significantly violated	Standard (Roman)
Info	insights about aspects of system operation	Italic

Informational (Info) alerts also highlight the configuration of Functionally Determined Constraint Levels (FDCL).

Designs with values outside their valid range are likely physically impossible. In spring design, negative values for wire diameter, coil diameter and number of coils are obvious examples. Other situations, for example where an increase in wire diameter results in a negative value for coil inside diameter or an increase in force at the second load point takes a compression spring below its solid condition may be a bit less obvious.

If started from a design with one or more values outside their valid range the Search feature may not be able to resolve the problem. In this situation, Search finishes with a different design point that is also invalid and with a message to correct the invalid condition manually. In order to proceed with a new Search, identify the source of invalid values and manually enter more appropriate values. As zero and negative numbers are a common source of invalid values, look for those first.

In order to avoid numeric difficulty when starting from a physically unrealistic situation, alerts of error (Err) severity may block operation of the Seek and Trade features. In order to proceed with Seek and Trade it will be necessary to identify the source of errors and manually provide more appropriate values.

The Value field of the Alerts presentation allows in-place adjustment of the associated variable's value and constraint levels. Select this field to get a value change dialog box that operates the same as the corresponding fields on the main pages (Advanced and Calculator Views). Where possible, the color of the number presented in the value field tracks the color of the multi-colored Feasibility Status Indicator.

Where possible, the linked detailed entries (below) provide specific guidance in moving to values that will resolve the alerts.

On this page (design type independent alerts):

On other pages (design type specific alerts):

Alert entry #ODOP01

Objective Value is Infinity

The Objective Value can become Infinity when numerical difficulties such as division be zero are encountered while solving the design equations.

Other entries in the Alerts panel may provide more specific details about which variables are causing the problem as well as specific guidance on how to resolve the situation.

An Objective Value of Infinity will cause a warning message when using the Search (solve) feature (Search button or Action : Search menu).

See also:

Terminology - Objective Function, Objective Value

Alert entry #ODOP02

Objective Value is Not a Number (NaN)

The Objective Value should not be able to achieve a value of NaN. If you are able to repeat this situation, please contact customer support.

See also:

Alert entry #ODOP03

Invalid - Value less than limit

The value of the associated variable is less than the validmin limit as defined in the design type's initialState.

This is a generic alert message so guidance on how to resolve this condition is not available here. Look for other alert messages as they might provide more specific advice. Look for zero or negative values. Undoing or reducing the size of recent changes may be helpful.

This alert means that the mathematical model for this design is not valid for the current set of inputs. Given the current set of Independent Variables, the design is likely outside the limits of physical reality. For example, in coil spring design, outside diameters (OD_FREE) less than twice the wire diameter (Wire_Dia) will produce a negative inside diameter, an impossible situation. Multiple Invalid messages may cascade out of a single out-of-range input value.

This condition may produce a warning message or even block the Seek and Trade features from starting.

See also:

Terminology - Validity

Alert entry #ODOP04

Invalid - Value greater than limit

The value of the associated variable is greater than the validmax limit defined in the design type's initialState.

This alert means that the mathematical model for this design is not valid for the current set of inputs. Given the current set of Independent Variables, the design is likely outside the limits of physical reality. For example, in coil spring design, outside diameters (OD_FREE) less than twice the wire diameter (Wire_Dia) will produce a negative inside diameter, an impossible situation.
Multiple Invalid messages may cascade out of a single out-of-range input value.

This condition may produce a warning message or even block the Seek and Trade features from starting.

See also:

Terminology - Validity

Alert entry #ODOP05

Invalid Constraint - Less than limit

The value of the associated constraint is less than the validmin limit for the associated variable as defined in the design type's initialState. The problem is in the constraint (MIN or MAX) value, not the value of the variable itself.

This means that, given the current constraint value (for example, a MIN value that allows a negative diameter), the design could be taken outside the limits of physical reality. The mathematical model for this design is not valid for values outside these these limits.

Look for zero or negative numbers in the MIN field of the associated variable. Change to positive, non-zero numbers as appropriate. Look for other messages as they might provide more specific advice. Undoing or reducing the size of recent constraint changes may be helpful.

See also:

Terminology - Validity

Alert entry #ODOP06

Invalid Constraint - Greater than limit

The value of the associated constraint is greater than the validmax limit for the associated variable as defined in the design type's initialState. The problem is in the constraint (MIN or MAX) value, not the value of the variable itself.

This means that, given the current input value, the design could be taken outside the limits of physical reality. The mathematical model for this design is not valid for values outside these these limits.

Look at the MAX constraint field of the associated variable. Adjust it as appropriate. Look for other messages as they might provide more specific advice. Undoing or reducing the size of recent constraint changes may be helpful.

See also:

Terminology - Validity

Alert entry #ODOP07

Inverted Constraint Range / Constraint Inconsistency

Constraints on the associated variable are inconsistent. Specifically, the MAX constraint value is less than the MIN constraint value.

This inconsistency may block the Search, Seek and Trade features from starting.

To resolve the situation, change one or both of the associated variable's constraint values. Increase the MAX value and / or decrease the MIN value until there is no overlap.

See also:

Alert entry #ODOP08

Constraint MIN violation

The associated variable's MIN constraint is violated by more than a trivial amount.

In order to resolve this alert:

Use the Search feature (see next paragraph)
Allow smaller values of the associated variable by decreasing the MIN constraint value.
Disable the constraint

It is quite possible that the constraint violation in question was created by use of the Search feature. In that case, further use of Search without introducing other changes is unlikely to be helpful. The most productive course of action may be to Free one or more variables currently in Fixed status or relax other, perhaps seemingly unrelated, violated constraints and then run Search again.

When Search returns a design judged to be NOT FEASIBLE, constraint(s) with the largest violations are the most leveraged and should be examined first. The full set of constraint violations is visible in Advanced View. In Calculator View, individual constraint violations are displayed in the Value Input dialog that results when selecting (clicking on) an Independent or Dependent Variable.

If Search has returned a design with violated constraints and judged to be NOT FEASIBLE, it is possible that too many variables in Fixed status have caused the design to become over-specified. If it it not possible to completely Free one or more variables currently in Fixed status, perhaps it would be helpful to replace a Fix with MIN and MAX constraints that allow a range of flexibility. Additional information on over-specified designs is available in the Design situations Help entry.

See also:

Alert entry #ODOP09

Constraint MAX violation

The associated variable's MAX constraint is violated by more than a trivial amount.

In order to resolve this alert:

Use the Search feature (see next paragraph).
Allow larger values of the associated variable by increasing the MAX constraint value.
Disable the constraint.

See also:

Alert entry #ODOP10

Fix Violation

The associated Dependent Variable is in Fixed status. Its value differs from the target value established by the Fix by more than a trivial amount.

In order to resolve this alert:

Use the Search feature (see next paragraph).
Change the Fix target value to something more consistent with what can be achieved within the remaining constraints and Fixes.
Disable the Fix.

It is possible that the Fix violation in question was created by use of the Search feature. In that case, further use of Search without introducing other changes is unlikely to be helpful. The most productive course of action may be to Free one or more variables currently in Fixed status or relax other, perhaps seemingly unrelated, violated constraints and then run Search again.

See also:

Alert entry #ODOP11

Not a Number (NaN)

The value of the associated variable is Not a Number (NaN). This is a computational error condition that may cascade to other variables.

In most cases, the best way to resolve this alert is to revert the most recent change to a variable. If that works, try establishing values that are part way to the value causing the problem. It is possible that using the Search feature could resolve the alert. It is also possible that use of the Search feature could create this alert. In that case, it may be possible to clear the alert by making small changes to one or more Independent Variables. If all else fails and a Search or Seek operation has been previously executed in the current design session, the AutoSave feature may allow you to fall back to a previous design.

The most likely source of this condition is user input that creates a mathematical difficulty such as division by zero. For example, in round wire coil springs, if the value of OD_Free is exactly twice the value of Wire_Dia, the associated ID_Free will have a value of exactly 0.0. This will likely create a division by zero situation in the calculation of other variables. NaN can appear when mathematical operations involve multiple infinities.

As it is possible to Save or Export a design with this condition, it is possible to encounter this alert on File : Open or File : Import of a previously saved design.

If you feel that this alert is not appropriate for your situation, please contact customer support.

See also:

Alert entry #ODOP12

No Free Independent Variables

If all Independent Variables (inputs) are in Fixed status, there is nothing left for Search to manipulate in order to achieve a feasible design. This condition may block use of the Search, Seek and Trade features.

It is possible that operation of the AutoFix feature has contributed to the situation.

In order to resolve this situation, put one or more Independent Variables in Free status. Specifically, uncheck the checkbox that is positioned between the associated variable's value and its units label. When in Calculator View, first click the variable in order to open its value change dialog box.

Rather than having a quantity set to a specific value with Fixed status, it may be appropriate to use Constraints to limit the range of values that quantity can achieve.

See also:

Alert entry #ODOP13

Functionally Determined Constraint Level (FDCL) is enabled

This variable has a functionally Determined Constraint Level (FDCL) configured and enabled.

This is not an error situation. Rather, this informational alert is intended to make sure that the user is aware that these FDCL type constraints are enabled.