odop

Open Design Optimization Platform (ODOP) - Coil spring design app; mechanical springs; compression spring, extension spring, torsion spring

View the Project on GitHub thegrumpys/odop

Errors  

This topic provides details for various messages produced by the software including each of the error conditions that may block the Action : Search, Seek, Trade and Catalog functions.

On this page:



Invalid Value messages

Each Independent Variable, Dependent Variable and numeric Calculation Input has a predefined range (validmin to validmax) for which it is considered to be valid. If a variable has a value outside this range, it is said to be "invalid". Just as Search will work to stay within constraint boundaries, it will work to keep each variable within its valid range.

Most commonly, negative values for quantities like diameters are considered to be invalid.

The Alerts facility will identify variables that have values outside their valid range. Press the Alerts button to see a list of active alerts. Any variables with values outside their valid range will be identified as "INVALID VALUE". Independent Variables can be modified directly and are sorted to the top of the list. As Dependent Variables cannot be modified directly, they are classified with "Info" severity and sorted to the bottom of the list. Select the entry in the "Value" column to modify the associated variable's value or the value of its constraints.

See Also:



Search Errors

Conditions that block operation of the Search feature include:

Follow the link above that corresponds to the message blocking Search.

Invalid Values

While usually a situation of having started with invalid values, it is possible for Search to return a design that contains invalid values. The Help links provided in the Alerts panel may provide specific recommendations to help clear the condition. In some cases it may be necessary to identify which input(s) are responsible for the invalid values and then manually adjust the value of those inputs so as to clear the invalid condition.

Objective Value not finite

A design with an Objective Value of infinity or NaN will not block Search. Rather, a warning pop-up will provide an opportunity to cancel the search request and examine the Alerts feature for details and context specific guidance.

Use the AutoSave feature to recover a design as it existed before a Search.

See Also:



Seek Errors

Conditions that block the operation of Seek include:

Follow the link above that corresponds to the message blocking Search.

Use the AutoSave feature to recover a design as it existed before a Seek.

See Also:



Trade Errors

Use the AutoSave feature to recover a design as it existed before use of the Trade feature.

See Also:



Catalog Errors

Use the AutoSave feature to recover a design as it existed before use of the Select Catalog feature.

See Also:



Objective Value not finite

A design with an Objective Value that is not finite (more specifically, a value of infinity or NaN) has numeric issues. One or more design variable values or perhaps a specific combination of values are causing the difficulty.

Continuing with Search may not result in an improvement.

Canceling Search will allow you to examine the Alerts panel for invalid values and associated guidance. Freeing one or more independent variables followed by a new search may result in an improvement.

Note that the AutoFix feature may contribute to unintentionally placing Independent Variables in Fixed status.

See also:



NaN = "Not a Number"

See also: