Difference between revisions of "Error Messages/42526"

Latest revision as of 19:37, 14 March 2016

Error text

 The right-hand side of the 'No_plane_reduction' constraint evaluated to a non-numeric value,
 «null», at coordinate:
  
     Time = 2015
  
 The optimization being solved was created using DefineOptimization from 'My_NLP'.

Cause

This message occurs when a non-linear optimization is being solved. During this solution process, the solver plugs solution candidates into the decision variables, and evaluates the constraints. For some value that tried, the indicated constraint evaluated to something that contained a non-numeric value, and hence the error. The error provides several important clues to help you pinpoint the problem. It shows what the bad value is («null» in this example), whether it occurred on the left-hand or right-hand side, and what coordinate it occurs at when the left-hand or right-hand side is array-valued.

Remedy

Adjust your model to eliminate the source of the non-numeric value.

If you are using Null to indicate that certain positions in an array-valued constraint are not to be used as constraints, then replace them with a vacuous constraint. An example is this -- instead of the constraint expression:

(if use_it then f(x) else null) = b

use:

(if use_it then f(x) else b) = b

@@ Line 1: / Line 1: @@
-= Error Text =
+[[Category: Error messages]]
-  The ''right-hand side'' of the ''No_plane_reduction'' constraint evaluated to a non-numeric value,
+== Error text ==
+<pre style="background:white; border:white; margin-left: 1em; font-style:italic">
+  The right-hand side of the 'No_plane_reduction' constraint evaluated to a non-numeric value,
   «null», at coordinate:
   &nbsp;
-      Time=2015
+      Time = 2015
   &nbsp;
-  The optimization begin solved was created using [[DefineOptimization]] from ''My_NLP''.
+  The optimization being solved was created using DefineOptimization from 'My_NLP'.
+</pre>
-= Cause =
+== Cause ==
-This message occurs when a non-linear optimization is being solved.  During this solution process,
+This message occurs when a non-linear optimization is being solved.  During this solution process, the solver plugs solution candidates into the decision variables, and evaluates the constraints.  For some value that tried, the indicated constraint evaluated to something that contained a non-numeric value, and hence the error.  The error provides several important clues to help you pinpoint the problem.
-the solver plugs solution candidates into the decision variables, and evaluates the constraints.  For
+It shows what the bad value is («null» in this example), whether it occurred on the left-hand or right-hand side, and what coordinate it occurs at when the left-hand or right-hand side is array-valued.
-some value that tried, the indicated constraint evaluated to something that contained a non-numeric
-value, and hence the error.  The error provides several important clues to help you pinpoint the problem.
-It shows what the bad value is («null» in this example), whether it occurred on the left-hand or
-right-hand side, and what coordinate it occurs at when the left-hand or right-hand side is array-valued.
-= Remedy =
+== Remedy ==
-Adjust your model to elimate the source of the non-numeric value.
+Adjust your model to eliminate the source of the non-numeric value.
+If you are using [[Null]] to indicate that certain positions in an array-valued constraint are not to be used as constraints, then replace them with a vacuous constraint.  An example is this -- instead of the constraint expression:
+:<code>(if use_it then f(x) else null) = b</code>
+use:
+:<code>(if use_it then f(x) else b) = b</code>
+==See Also==
+* [[DefineOptimization]]
+* [[Introduction to Optimizer]]
+* [[Display of constraint results]]
+* [[Objects and Values]]