To enter linear constraints via the red triangle menu, select Alter Linear Constraints from either the Prediction Profiler or Custom Profiler red triangle menu.
Choose Add Constraint from the resulting window, and enter the coefficients into the appropriate boxes. For example, to enter the constraint p1 + 2*p2 ≥ 0.9, enter the coefficients as shown in Figure 1.8. As shown, if you are profiling factors from a mixture design, the mixture constraint is present by default and cannot be modified.
Figure 1.8 Enter Coefficients
After you click OK, the Profiler updates the profile traces, and the constraint is incorporated into subsequent analyses and optimizations.
Constraints added in one profiler are not accessible by other profilers until saved. For example, if constraints are added under the Prediction Profiler, they are not accessible to the Custom Profiler. To use the constraint, you can either add it under the Custom Profiler red triangle menu, or use the Save Linear Constraints command described in the next section.
If you add constraints in one profiler and want to make them accessible by other profilers, use the Save Linear Constraints command, accessible through the platform red triangle menu. For example, if you created constraints in the Prediction Profiler, choose Save Linear Constraints under the Prediction Profiler red triangle menu. The Save Linear Constraints command creates or alters a Table Script called Constraint. An example of the Table Property is shown in Figure 1.9.
Figure 1.9 Constraint Table Script
The Constraint Table Property is a list of the constraints, and is editable. It is accessible to other profilers, and negates the need to enter the constraints in other profilers. To view or edit Constraint, right-click the red triangle menu and select Edit. The content of the constraint from Figure 1.8 is shown below in Figure 1.10.
Figure 1.10 Example Constraint
The Constraint Table Script can be created manually by choosing New Script from the red triangle menu beside a table name.
Note: When creating the Constraint Table Script manually, the spelling must be exactly “Constraint”. Also, the constraint variables are case sensitive and must match the column name. For example, in Figure 1.10, the constraint variables are p1 and p2, not P1 and P2.